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
24-hour periods
Monitoring may continue in 24-hour periods while the internal balance is sufficient. Check order status: paused or cancelled monitoring should not be treated as active.
Ready to create a task?
Create an account, review available parameters, and see the final cost before confirmation.