Loading ServiceTooly
Scheduling & Field Work | Workspace

Review and resolve operational exceptions

Use the tenant-scoped exception queue to investigate failed or blocked workflow items, retry only safe work, and preserve the audit trail.

Sign in to your company workspace to use the related controls.

Open related section
Feature-specific ServiceTooly wireframe for Review and resolve operational exceptions
This wireframe is generated from the feature names and steps in this guide, so it stays aligned with the instructions even when labels vary by role or plan.

What this section includes

  • Tenant-scoped exception queue
  • Status and category filters
  • Safe retry or terminalization
  • Ownership and notes
  • Audit history
  • Super Admin global review

Start-to-finish instructions

  1. Open the queue

    Open Operations > Exception Queue and confirm the active company before reviewing any item.

  2. Filter the work

    Filter by status, category, severity, owner, and date so the intended exception is unambiguous.

  3. Inspect the evidence

    Review the source workflow, error, retry history, tenant scope, related record, and customer impact without exposing secrets.

  4. Choose the safe outcome

    Retry only an idempotent operation with its prerequisite corrected, or cancel, expire, acknowledge, or escalate the item according to policy.

  5. Confirm the audit trail

    Refresh the item and verify its new state, actor, timestamp, reason, and any resulting workflow status.

What success looks like

  • Workspace users see only exceptions belonging to their authenticated company.
  • Repeated actions do not duplicate work, and terminal items are not processed.
  • Super Admin review remains separate and fully audited.

Common problems

  • Do not retry an item that could duplicate a payment, message, call, invoice, subscription, or customer record.
  • A Super Admin can review platform-wide exceptions, but that does not authorize bypassing tenant or workflow safeguards.
  • Provider delivery remains disabled in staging unless an approved sandbox test explicitly enables it.