Monitoring health

12 eligible resolved tickets · 12 retained checks · 4 known sources

1 gap need attention

Coverage is limited to configured sources and eligible resolved tickets. Missing feeds and unknown populations remain outside this assessment.

Assessment scope and clocks

Known sources: helpdesk, payments, commerce, fulfillment; 12 eligible resolved tickets in 2 monitored categories, 12 retained instances. Snapshot freshness is reported per source; missing event feeds and unknown populations are outside this assessment. Computed Oct 30, 2026, 17:10 UTC (wall time); business/scenario time Oct 30, 2026, 17:16 UTC.

1 pending instance missed a scheduled re-check.

Source coverage and freshness

Recorded reads; clocks are labelled

helpdeskZendesk / GorgiasRead-only access recordedChecked Demo time · Oct 30, 17:16 UTC
Feed poll recorded (wall clock): Oct 30, 2026, 14:32 UTCRecord/list retrieval (business clock): Oct 30, 2026, 14:38 UTC
Event timing
Received (wall clock): Oct 30, 2026, 14:32 UTC; occurred (source clock): Oct 30, 2026, 14:38 UTC
Event processing detail
Received minus occurred: under a minute; scenario-clock offsets can affect this difference.
12 processed · 0 awaiting · 0 failed · 0 set aside
paymentsStripeRead-only access recordedChecked Demo time · Oct 30, 17:16 UTC
Feed poll recorded (wall clock): Oct 30, 2026, 14:32 UTCRecord/list retrieval (business clock): Oct 30, 2026, 14:38 UTC
Event timing
Received (wall clock): Oct 30, 2026, 14:32 UTC; occurred (source clock): Oct 30, 2026, 14:35 UTC
Event processing detail
Received minus occurred: under a minute; scenario-clock offsets can affect this difference.
2 processed · 0 awaiting · 0 failed · 4 set aside
commerceOrder management (Shopify-style)Read-only access recordedChecked Demo time · Oct 30, 17:16 UTC
Feed poll recorded (wall clock): record retrieval only; no feedRecord/list retrieval (business clock): Oct 30, 2026, 14:38 UTC
Event timing
Received (wall clock): none; occurred (source clock): unknown
Event processing detail
Received minus occurred: —; scenario-clock offsets can affect this difference.
0 processed · 0 awaiting · 0 failed · 0 set aside
fulfillmentFulfillment / carrier APIRead-only access recordedChecked Demo time · Oct 30, 17:16 UTC
Feed poll recorded (wall clock): record retrieval only; no feedRecord/list retrieval (business clock): Oct 30, 2026, 14:38 UTC
Event timing
Received (wall clock): none; occurred (source clock): unknown
Event processing detail
Received minus occurred: —; scenario-clock offsets can affect this difference.
0 processed · 0 awaiting · 0 failed · 0 set aside

Mode (demo fixtures or live credentials) is shown on Connections; this page reports health regardless of mode. read-only every connector.

Eligibility

Who owes a verification, before any verdict

Resolved tickets12all categories, systems of record

In monitored categories12100% of resolved

Eligible12100% of monitored categories · match an approved trigger

Excluded · no approval0resolved without agent approval; no obligation

Not monitored0categories without an approved contract

Eligible, no instance yet0created by the next sweep

Contracts: 2 monitored of 2 · 0 awaiting approval · 0 paused.

Instances

12 evaluated

Verified867% of evaluated

Violated217% of evaluated · each opened an incident

Pending11 overdue for a re-check · 0 past give-up age

Indeterminate11 awaiting review · 0 reviewed

Incidents: 2 open · 0 acknowledged · 0 snoozed · 0 resolved.

Events, worker and retry policy

Events

Webhooks and polled feeds

Processed14created or updated an instance

Awaiting0none waiting

Failed0after retries; reconciliation covers them

Set aside4with a recorded reason

Why events were set aside

no pending instance waits on this payment4

Worker

Shared job queue

Queued0waiting for a worker

Running0lease-protected

Done16last 3 h ago

Failed0no failures

Deadline: Deadline = the ticket's resolution time plus the contract's deadline. The same clock (the systems of record) is used for evaluation, re-checks and incidents.
Re-check: A pending instance is re-checked at the later of its deadline and an exponential backoff (contract.instance.initialRetrySeconds doubling to maxRetrySeconds), or sooner when a payment event names its charge.
Give-up: If nothing is observable by contract.instance.maxAgeSeconds after resolution the instance becomes indeterminate. No instance stays pending indefinitely.
Retention: New instances retain the evaluation snapshot and evaluated contract version. A missing historical version stays unknown; current policy is only a labelled comparison. Evaluation snapshots are business records, not application traces.