Skip to main content

Troubleshooting

Common scheduler problems and how to resolve them.

"My schedule isn't firing"​

  1. Check the status on the detail page. DRAFT and PAUSED schedules don't fire — activate or resume.
  2. Check next execution at. If it's empty or in the past, the schedule is misconfigured (e.g., end date already passed, no future window in WINDOWED, RRULE produces no future occurrences).
  3. Check maintenance mode. If a workspace admin enabled maintenance mode, no schedules fire until it's disabled. The list view shows a banner.
  4. Check the circuit breaker for the schedule. If the breaker is OPEN, runs are short-circuited until cooldown — open the schedule detail page, look at the breaker panel, and Reset it once the underlying target is healthy again.

"It fired but the executor failed"​

Open the latest execution. The error message and stack trace point to the cause.

  • Webhook 4xx — the target rejected the request. Check the URL, headers, payload template, and any signing/auth secrets on the schedule.
  • Webhook 5xx / timeout — the target is broken or slow. Retries will pick this up; if they all fail you'll see the DLQ entry.
  • Internal API GraphQL errors — usually a permissions or schema mismatch. The internal gateway returns the operation name and field path.
  • the event bus topic unreachable — the messaging cluster is degraded. Check the workspace status page.

"The schedule is auto-disabled"​

Auto-disable triggers after autoDisableAfter consecutive failures. The schedule moves to DISABLED and stops firing. Fix the underlying issue, then Activate the schedule again.

"My execution succeeded but did the wrong thing"​

Open the execution detail and inspect the config snapshot. This is the exact configuration the schedule had at fire time — not the current configuration. If the snapshot is wrong, the schedule was edited since the run; check the versions tab to see what changed.

"I can't see the schedule someone else created"​

Scheduler is workspace-scoped. You'll only see schedules in the workspace your session is currently in. Switch workspaces in the top-right.

"The DLQ keeps filling up"​

Pattern usually points to one of:

  • A flaky external dependency the executor calls
  • A misconfigured schedule that always fails
  • A retry policy that's too aggressive for a known-flaky target

Tighten the schedule's retry policy or fix the upstream. If a single schedule is the source, Pause it until you've fixed the root cause.

When to escalate​

Open a ticket with workspace platform support if:

  • Multiple schedules across the workspace stop firing simultaneously (likely engine-level outage)
  • The scheduler subscriptions never reconnect after a network blip
  • The DLQ shows entries with no underlying execution (data integrity issue)