Obvious/Help Center

Scheduled Task Didn't Run

Published February 27, 2026 · Last updated March 5, 2026 · 2 min read

Your task has a schedule configured, but it didn't run when expected. Here's how to figure out why.

The schedule is disabled

What you see: The task exists with a schedule, but no execution history appears.

What's happening: The schedule toggle is off. Obvious skips disabled schedules — no thread is created, no execution is queued.

How to fix it:

  1. Open the task in your project.
  2. Check the schedule trigger for an Enabled status.
  3. Enable the schedule. Obvious recalculates the next run time immediately.
  4. Verify the next scheduled run time looks correct.

Timezone mismatch

What you see: The task runs, but at the wrong time — hours earlier or later than expected.

What's happening: The schedule's timezone doesn't match yours. A task set to 9:00 AM in America/New_York fires at 6:00 AM in America/Los_Angeles. Obvious uses the timezone stored with the schedule, not your local timezone.

How to fix it:

  1. Open the task and check the configured timezone.
  2. Update it to your intended IANA timezone — like America/Chicago or Europe/London, not abbreviations like "CST."
  3. Save. Obvious rebuilds the next run time with the corrected timezone.

Tip: For cross-timezone teams, pick one standard timezone for all scheduled tasks. UTC works as a neutral choice.

Execution error

What you see: A thread was created for the run, but the task didn't complete — or completed with errors.

What's happening: The schedule triggered correctly, but something failed during execution. Common causes: deleted data the task references, a disconnected integration, or a step the agent couldn't recover from.

How to fix it:

  1. Find the execution thread. Scheduled runs create threads named Scheduled: [Task Name].
  2. Open it and read the agent's output — the error is usually in the last few messages.
  3. Fix the underlying issue: reconnect the integration, restore missing data, or update the task steps.
  4. Run the task manually to confirm it succeeds before relying on the schedule again.

Still stuck?

If the schedule is enabled, the timezone is correct, and the execution thread shows no errors — reach out to support with the task name, project, and the expected run time.

Next steps

Was this helpful?