Help centre · Troubleshooting

Why has my run not started?

The three reasons a run waits, and how to tell which one applies to you.

A run shown as queued is waiting for a slot. Three possible causes, in order of frequency: you have already reached your concurrent-run limit, your monthly allowance is used up, or the platform is momentarily busy.

How many runs can I execute at once?

Your plan sets a ceiling on concurrent runs, and you can lower it yourself in Pipeline → Execution — never raise it past the plan. Runs beyond it wait for a slot to free up; they are not lost.

This is a shared-capacity limit, not a billing one: what counts against your plan is runs per month, not how many run at the same time.

How do I know it is my monthly allowance?

The gauge at the top of the home page says so. If it is full, a launch is refused with an explicit message rather than queued — a run waiting forever with no visible reason would be worse. See Allowances and plans.

Can I push one run ahead of the others?

Not manually. Within an account, the order is first come, first served. Higher plans get queue priority on busy days, but that plays out between accounts, not among your own runs.

What if my run has been queued for a very long time?

Cancel it and launch again. A queued run has consumed nothing yet: cancelling costs nothing and does not count against your allowance. If it keeps happening, write to us with the run's identifier.