Executions queued n8n cloud version

Describe the problem/error/question
in my cloud n8n there is only 1 workflow.
This workflow helps me create AI-generated videos.

and it occurs over and over again that there are executions queued (attached screenshot).
Even if there are no other running executions.

What is the reason for that and how can I prevent that?

What is the error message (if any)?
“queued”

Please share your workflow/screenshots/recording

Share the output returned by the last node
there is no output

Debug info
core
n8nVersion: 2.0.3
platform: docker (cloud)
nodeJsVersion: 22.21.0
nodeEnv: production
database: sqlite
executionMode: regular
concurrency: 20
license: enterprise (sandbox)
storage
success: all
error: all
progress: false
manual: true
binaryMode: filesystem
pruning
enabled: true
maxAge: 720 hours
maxCount: 25000 executions
client
userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36
isTouchDevice: false
Generated at: 2025-12-23T05:24:24.751Z}

Hey, I’ve actually dealt with this exact same problem before so I think I know what’s up.

It’s probably not really about your specific integrations or tools - I’m pretty sure it’s your n8n database setup. If you’re using the default SQLite database, that’s definitely your problem. I had the same frustrating experience where my workflows used to finish in like 5-10 minutes and then suddenly they started taking literal hours to complete.

SQLite just can’t handle running multiple things at once very well, especially when you’re doing workflows with a lot of data processing or API calls. It becomes this huge bottleneck because it locks the whole database when it’s writing stuff, so when you have a bunch of executions running or you’re processing heavy data loads, everything just starts piling up and slowing to a crawl.

I switched over to PostgreSQL and honestly it was a massive difference. Everything started running smooth again because PostgreSQL is actually built to handle concurrent stuff and can deal with the load way better. Pretty much everyone recommends it if you’re running in production or doing workflows regularly.

The migration itself isn’t that bad - you basically just need to spin up a PostgreSQL database and update your n8n environment variables. One thing to know though - you’ll have to rebuild your workflows since the data doesn’t automatically transfer over.

Oh and also check if your execution history is super bloated in your current SQLite database - that can slow things down a ton too.