What you are told, and when
Notices are kept rare on purpose, so the ones that arrive matter.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- One notice when an incident opens. Not again while the same fault lasts.
- One notice for every autopilot outcome.
- One notice when a downstream reader stops or falls behind, and one when it reads again.
- One notice when a pipeline watch starts, when it sees drift and when it closes.
- One notice when a data check finds rows lost or duplicated, and for every check a person asks for.
- When paging is on: the page, each escalation, and a resolved notice when the system recovers.
- No notice for a single bad check, for a fault that clears before it is confirmed, or for a normal recovery.
What you should see: The console always shows the full history, whether or not a notice was sent.
What it can and cannot do
Can
- Tell a person once per incident and once per autopilot outcome.
Cannot
- Tell you about a single bad check or a fault that cleared before it was confirmed.
Related articles
- Notices in Microsoft TeamsVarqeni posts a card to a Teams channel when it opens an incident, when the autopilot acts, and when a downstream reader needs a person.
- How an investigation startsVarqeni opens an investigation when a fault holds for two checks in a row, and not again for the same fault.
Still stuck? Contact support or email info@fortisdatagroup.com.