Unable to run Automations

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Getting “Concurrent agent limit reached” error despite not running any other Automations.

Steps to Reproduce

Setup Automation to trigger from slack.
After few successful workflows, they stop working completely.
Claiming concurrent usage despite only 1 Automation active.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

cursor. com/automations

For AI issues: which model did you use?

Opus

Additional Information

cursor. com/automations/9ed1c04b-4e5b-4ac4-aff5-1fdc6d5972b5/runs

Using company Team account. We still have on-demand budget available.

Does this stop you from using Cursor

Yes - Cursor is unusable

What is the concurrent Automation limit for an organization Team plan?

Is there a maximum timeout for a stuck Automation?

Found this stuck Automation created by my colleague but I can’t cancel it and it seems to block any Automation usage across our org:

Hi @jozef!

There are a few compounding issues here:

  • There is a known bug where the concurrent agent check falsely counts stale IDLE agents toward the limit.
  • Only owners of an automation, as well as Team Admins, can cancel an ongoing automation. This is why you couldn’t cancel your colleague’s automation.
  • Most importantly, your team has used 100% of its on-demand usage limit. Even if you haven’t reached your personal limit, you’ll be blocked by the team’s limit.

I’d suggest reaching out to your team admins to review and raise your team’s on-demand limit. Alternatively, you can contact [email protected] for more details about your limit and options for increasing it.

Once the on-demand limit is resolved, please try running another automation.

Thank you @Colin , I’ll reach out to our admins to bump the limits for this month. I was a bit confused since usage screen says I spent only $11.8 out of our $500 monthly on-demand limit. I understand now that thats only my portion of on-demand across the whole team?

Thanks for confirming the bug with the stale agents.

It is confusing, and I would really like us to indicate that your team has reached its limit, even if we don’t display the actual limit (as some organizations may be sensitive about this information)!