If you're noticing that access events aren't showing up in your Access History section, you're not alone. This is a common issue that typically stems from a few specific problems. The good news is that most of these can be resolved with some straightforward troubleshooting.

Common Reasons Your Access History Isn't Updating

There are several culprits that could prevent access events from appearing in your logs. Understanding what's happening behind the scenes will help you pinpoint the exact issue.

Gateway or Device Connectivity Issues

The most frequent cause is that your gateway or devices have gone offline or are experiencing unstable network connectivity. When your gateway can't maintain a stable connection, it can't communicate access events back to the system. Similarly, if your access devices themselves are offline, they won't be able to log attempts in the first place.

Network or Firewall Restrictions

Sometimes your gateway is online, but it's unable to communicate with the cloud due to firewall rules or network policies blocking the connection. This creates a situation where access might be happening physically at the door, but the event data never reaches your portal.

Temporary Synchronization Delays

Even when everything is working correctly, there can be a slight delay in syncing access events to your portal. This is usually temporary, but it's worth ruling out before assuming something is broken.

Access Method Complications

In some cases, specific access methods like BLE Tap Access may require additional investigation. You might see successful access at the door, but the logs aren't reflecting those attempts, which points to a logging or communication gap specific to that method.

How to Diagnose the Problem

Start by checking the basics. Verify that both your gateway and all devices are actually online and connected. A quick way to confirm this is to check your device status in the admin panel.

Next, examine your network connection. Make sure your gateway has active internet access. If you're on a corporate network or behind a restrictive firewall, confirm that network policies aren't blocking communication between your gateway and the cloud servers.

Then, test whether access is actually working at the door level. Have someone attempt to access using a credential you know is valid. If the access succeeds but still doesn't appear in your history, you've narrowed down the issue to a logging or communication problem rather than an access denial problem.

Steps to Resolve the Issue

Start with the simplest solutions first. Wait a few minutes, then refresh your Access History page. Sometimes this is all you need to see newly synced events appear.

If that doesn't work, restart your gateway to re-establish its connection to the cloud. This often resolves temporary communication hiccups.

Check your firewall and network settings to ensure they're not blocking the gateway's outbound communication. You may need to work with your IT team if you're unsure about your network configuration.

Finally, if you're still not seeing events after these steps, contact support with details about what you've already checked. Include information about your gateway status, network connectivity, and whether access is physically working at the door even if it's not logging.

Keeping your access history accurate depends on having a healthy connection between your devices, gateway, and cloud system. Most update delays resolve once you've confirmed these three components can communicate with each other.