COB diagnostic tool

T24 COB Failure Diagnostic Wizard

Turn a vague report such as “COB is stuck” into prioritised safe checks, evidence to capture, and an escalation summary without sending incident data anywhere.

Start the diagnostic

This browser-only tool structures first checks. It does not connect to T24, transmit answers, store incident data, or replace an approved operational runbook.

What the wizard covers

  • COB not started and missing trigger paths
  • Stopped services and unexplained service-state mismatches
  • Long-running or potentially stalled jobs
  • Explicit failures and first-error analysis
  • State alignment after a database or application restore
  • Green status with missing outputs or failed reconciliation

For deeper background, read what COB is in T24, why a green batch status can be misleading, and the incident escalation checklist.

Privacy and operational safety

Answers remain in the current browser tab. The copied summary is deliberately generic, but remove customer data, credentials, account numbers, message payloads, internal hostnames, and environment-specific secrets before sharing it.

This is a diagnostic aid, not an automated recovery system. Any action that changes processing state must follow local approval and runbook controls.

Next useful tools

T24 Date Converter
Confirm and compare T24 business dates
Enquiry & Version Reference
Find useful enquiries for evidence gathering

Related articles

Understand the COB processing modelVerify completion beyond a green statusBuild a useful escalation pack