Why Do Newly Created Events Appear with some delay in the REST API as compared to UI?

This behavior occurs due to differences in how data is served to the Resilinc User Interface (UI) versus the REST API.

How the UI Retrieves Data:

• The Resilinc UI pulls data directly from the core backend data tables.
• As soon as an event is created and stored, it becomes visible in the UI.

How the REST API Retrieves Data:

• The REST API retrieves data from view tables, not directly from the backend tables.
• These view tables are refreshed after the backend data tables are updated.
• The refresh process is sequential, meaning View tables are updated one at a time
• Larger tables take longer to refresh

Why the Delay Happens:

• Event data is high-volume, especially during active risk periods.
• Although data begins flowing to the view tables shortly after event creation, the update may be queued behind other table refreshes.
• As a result, newly created events may not appear in API responses immediately, even though they are already visible in the UI.
• This delay is expected system behavior and does not indicate data loss or API malfunction.