Automation issues

Use this page when an automation doesn't run, runs at the wrong time, uses the wrong repo or agent, or you can't find the workspace it created.

Automations show up as Workflows in the app sidebar; "automation" is the same thing underneath. Every run creates a brand-new workspace and session, it never reuses an old one, so "where did the output go" usually means "which new workspace did this run create."

Check:

• The schedule is what you think it is. Schedules run hourly or daily (daily can be limited to weekdays or weekends). There's no support yet for more complex recurrence or event triggers like "on PR open" or "on Sentry alert." If an automation only runs when you click Run now, that's expected unless you've attached a schedule.
• The owner and run location match what you expect. Personal automations run with your own setup and are visible only to you. Team automations run in your organization's shared cloud, and only an org admin can create or edit one (any member can still trigger a manual run).
• A local automation's app was actually open. Local automations only fire while the desktop app is running on your machine, which makes them the least reliable choice for anything scheduled. If it needs to run unattended, move it to personal or organization cloud.
• The target repo and its cloud setup still exist. If the repository was disconnected, renamed, or its cloud environment was never set up, the run fails before it gets to the agent. See cloud workspace issues.
• The agent and model are still available. If the automation's saved run configuration points at an agent or model that's no longer authenticated, the run fails the same way a manual chat would. See agent credential issues.
• Credentials are scoped for where the automation runs. A personal automation uses your own credentials. A team automation running in organization cloud needs credentials that are actually available there, which may mean an org-shared credential rather than your personal one.
• You're looking in the right place for the result. A personal automation's workspace is private, visible only to you. A team automation's workspace lands in the organization's shared, unclaimed pool until a teammate claims it, at which point it belongs to them.

For the full model behind schedules, ownership, and run location, see Automations and team workflows.