Section 1
A check is not the same as an event
A check records the state available to the service at a point in time. An event represents a detected change between checks. No new event does not mean continuous per-second observation.
Section 2
Interpret timing correctly
History time relates to the service check or recorded event. It does not establish the exact in-game second of a change or guarantee that the state remained unchanged afterward.
Section 3
Telegram and the dashboard
Dashboard history remains the primary result. Telegram can report supported events, but delivery depends on an external channel and connectivity.
Section 4
Prepaid check packages
Shield checks are prepaid in packages costing 1 kopek. The number of checks per package is shown in the interface. A new package is charged when a result arrives and no prepaid checks remain. Remaining checks belong to this order only and cannot be transferred to other orders. Unchanged statuses and reused results also consume a check. Monitoring pauses only when no checks remain and the balance cannot cover a new package.
Ready to create a task?
Create an account, review available parameters, and see the final cost before confirmation.