Docs / CAMZA.AI
Test the moments between connected and disconnected.
Offline behavior is a property of the complete deployment, including cameras, processing, storage and message destinations. Camza’s production behavior has not yet been confirmed. Use this checklist to test each interruption separately and record what continues, what is delayed, what is lost and what happens after the connection returns.
UPDATED
Run a failure matrix
| Interrupt | Observe during the outage | Observe after recovery |
|---|---|---|
| Camera stream | Visibility of stream loss; processing state | Reconnect and missing interval |
| Site internet | Local functions and queued work | Order, duplicates and delayed messages |
| Processing host | Recording ownership and failure notice | Restart and retained state |
| Action destination | Timeout and delivery status | Retry behavior and duplicate effects |
| Authentication | Failure visibility and access revocation | Recovery with rotated credentials |
Preserve the event time
Record both the event time and delivery time in a test. A message delivered after an outage may be technically successful but no longer useful for an immediate response. Agree the handling of stale events with the operational owner.
Confirm the architecture first
This checklist does not promise local processing, offline actions, queuing or automatic recovery. Those behaviors need deployment-specific evidence.
A few useful questions.
Can I try this on my own cameras?
Start with a compatibility request. Share camera models, firmware and the event you want to find. An evaluation needs an agreed scope before any camera access is arranged.
Is the website demonstration a product benchmark?
No. The sample demonstration uses illustrative scenes and predefined events. It does not measure accuracy, response time or compatibility on your cameras.
What should we agree before a pilot?
Agree which streams are in scope, who can access the data, where processing runs, retention and deletion, expected outcomes, and the person responsible for reviewing results.
YOUR CAMERAS. YOUR CONTEXT.
Start with one
useful question.
A camera inventory. An event to find.
A clear next step for your team.