Skip to Content
Docs are being rebuilt — start at Introduction → How it works.
TroubleshootingTask failed

Task failed

A one-time or scheduled task shows a failed status in its history, or it completes without producing the expected output.

Likely causes

  • Background job processing is down, so the task never executed.
  • The workspace ran out of credits mid-run, or the user who owns the task hit their monthly cap.
  • The task’s agent could not reach a required tool, integration, or knowledge base.
  • The task instructions were ambiguous and the agent finished early.
  • An external trigger fired with a payload the task did not expect.

Step-by-step fix

  1. Read the run record

    Open Task history & logs and select the failed run. The record shows the status and the error or final output. Most failures explain themselves here.

  2. Confirm background jobs are healthy

    Tasks run through TeamMate’s background job processor (Inngest). Open Settings → Diagnostics and test the Inngest connection. If it reports unhealthy, scheduled and one-time tasks will not run until it recovers.

  3. Check credits and caps

    A run that stops partway often means the workspace balance hit zero or the owner reached their monthly cap. Verify both at Settings → Usage & Billing. See Credit / quota issues.

  4. Verify the agent's dependencies

    If the agent needs a connected app or a knowledge base, confirm those are still attached and connected. A disconnected integration surfaces as a tool error inside the run. See Integration disconnected.

  5. Re-run after fixing

    Once the cause is addressed, trigger the task again from its detail page. For recurring tasks, the next scheduled run will pick up the fix automatically.

Where to look

Agent not respondingWorkflow stuck