Skip to main content
Most task issues come down to plan eligibility, timezone mismatches, connector authorization, or prompt quality. Work through the relevant section below.
If you don’t see a New Task button or the Tasks page shows a paywall message:
  • Tasks require a Pro plan or above. Free plan users do not have access to the Tasks feature.
  • To upgrade: go to Settings → Account → Subscription and select a Pro plan.
If you are already on Pro and the button is still missing or grayed out:
  1. Refresh the page (Cmd/Ctrl + R)
  2. Log out and back in — plan changes sometimes require a fresh session
  3. Clear your browser cache
If the issue persists after those steps, contact ZeroTwo support.
If a task’s scheduled time passed and it did not run:
  1. Check if the task is paused — open the task from /tasks. If its status is Paused, toggle it back to active from the detail panel.
  2. Verify your timezone — tasks run in your configured account timezone. If your timezone is set to UTC but you intended an 8 AM run in EST, the task ran 5 hours earlier than expected.
    • Check and update timezone: Settings → General → Timezone
  3. Check your subscription — if your plan was downgraded or a payment failed, task execution may have been suspended. Check plan status at Settings → Account → Subscription.
  4. Check the Completed tab — the task may have run successfully and moved to Completed while you were looking at the Upcoming tab.
  5. Check chat history — task results go to /c. Search for an auto-named chat matching your task’s first line. The task may have run without triggering a notification.
If the task ran (status shows Completed) but you can’t find the output:
  1. Look for an auto-named chat — navigate to /c (Chat History). Task results are posted as a new chat named after the first line of your task description.
  2. Use chat history search — search for keywords from your task description or that would appear in the expected output.
  3. Check the task’s View History — open the task from /tasks → click View History — each run entry links directly to the result chat.
  4. Wait and refresh — there can be a brief delay between task completion and the result appearing in chat history. Wait a minute and refresh /c.
  5. Check if the task failed — in the task’s View History, look for runs marked as Failed. A failed run may not have produced output.
If a recurring task ran correctly for a while and then stopped:
  1. Check if it was accidentally paused — open the task from /tasks and confirm its status is not Paused.
  2. Check your subscription — recurring tasks require an active Pro plan. If your subscription lapsed or was downgraded, tasks stop executing. Check at Settings → Account → Subscription.
  3. Check connector authorization — if your task uses a connected app and that connector’s OAuth token expired, the task may fail silently. Go to Settings → Connectors, find the relevant connector, disconnect it, and reconnect to refresh the token.
  4. Review execution history — open the task → View History to see when it last ran successfully and whether subsequent runs are marked Failed with error details.
If the task ran successfully but the output isn’t what you wanted:
  1. Add more specific instructions — vague descriptions produce generic output. Review the Create a Task guide for prompt patterns that produce better results.
  2. Specify the output format explicitly — tell ZeroTwo exactly how you want the result structured: 
    Format the output as:
- Section heading (bold)
- 3-bullet summary
- One-sentence conclusion
  3. Test the prompt manually — before scheduling, run the task description as a normal chat message to verify the quality. Once you’re satisfied with the output, create the scheduled task.
  4. Check connector data — if the task uses connectors and the output seems like ZeroTwo couldn’t access the expected data, verify the connector is still authorized in Settings → Connectors.
  5. Add example outputs — including a short example of the ideal output format in your task description helps ZeroTwo understand your expectations.
If a custom cron schedule isn’t running at the intended times:
  1. Validate the expression — use crontab.guru to verify that your cron expression evaluates to the schedule you intend.
  2. Use 5-field syntax — ZeroTwo uses standard 5-field cron format: 
    minute hour day-of-month month day-of-week
    A 6-field expression (with seconds as the first field) is not supported.
  3. Remember timezone — cron expressions are evaluated in your account timezone (Settings → General → Timezone), not UTC.
  4. Common mistakes to check:
    • 0 8 * * 1 = Mondays at 8 AM (day-of-week: 0=Sunday, 1=Monday, …, 6=Saturday)
    • 0 8 1 * * = 1st of every month at 8 AM, not every Monday
    • */15 * * * * = every 15 minutes — confirm this frequency is what you want
  5. Verify the next run time — after saving a custom cron task, the task detail panel shows the next scheduled run time. Confirm it matches your expectation before leaving.

​
Getting More Help

If none of the above resolves your issue:
  • Review Create a Task for best practices on writing task descriptions
  • Review One-time vs. Recurring for scheduling guidance
  • Contact ZeroTwo support at support@zerotwo.ai and include:
    • The task description (redact any sensitive data)
    • The schedule and your account timezone
    • A screenshot from the task’s View History panel
    • A description of the expected vs. actual behavior