Kapta · 15/09/2026
Outage behaviour should be agreed before installation. Local validation depends on the architecture and available data; an application's offline feature should not be assumed to exist in an integrated gate system.
Can visitors keep entering?
Assess the options with the operations team: directing visitors to assistance, staff verification or previously prepared local validation. Each has limitations. Information saved before an outage may exclude a recent purchase, cancellation or use at another entrance.
How can two disconnected readers avoid duplicates?
Without an up-to-date shared state, isolated entrances may not know that the same entitlement has already been used. The project should explain this limitation and define suitable procedures, such as temporarily centralising verification with one team. Absolute duplicate prevention should not be promised for every offline scenario.
What information should staff see?
Display the connection failure and the age of available information. Decisions made during the interruption should be identifiable, with a procedure for resolving exceptions. The integration should respect the safety and emergency mechanisms specified for the equipment and installation.
What should be tested when connectivity returns?
Reproduce an interruption during a scan and confirm how pending records recover, how conflicts are handled and how staff receive the outcome. Also test a booking sold during the outage. Ask Kapta to include network recovery and support responsibilities in the project scope.
