No search results mention execution timeout as a differentiator between paid tiers. The 5 min limit is probably on the Starter tier and possibly on Pro as well. The n8n documentation is not clear on this.
Seid ihr auf ein ähnliches Problem gestoßen?
Das scheint die neuesten Informationen zu sein (folge dem Thread)
Hello,
I have been searching for maximum workflow execution time and I keep finding outdated information; therefore, I would like to know if there is a fresh information from n8n team about this.
At some point it was 5m for a Starter plan, but my workflows are running for >1h without being stopped, so this is not true.
I was thinking that restrictions were removed completely, but documentation still says “For n8n Cloud users, n8n enforces a maximum available timeout for each plan.“ (Ref.: Set…
was darauf hindeutet, dass es kein Ausführungszeitlimit gibt
Hallo @LigiaAdam , willkommen!
Lies diese
I am working on Website scraper workflow where i will scrape webpages, personalize email and send emails.
I am fetching 500 records from apify/appollo. Then i am running Loop of these 500 items one by one and performing scraping, sending email etc. But this process is not running for all 500 items. It stops after 30-40 loops.
I am using starter plan of n8n. Tell me what could be the issue? I need to scrape all the urls present in the apify 500 items.
Thanks
A maximum execution time of 40 minutes is allowed in the Pro plan.
[image]
How exactly is this time measured? If I have a daily, time-controlled workflow that starts several subflows one after the other and takes longer than 40 minutes in total, but each subflow takes less than 40 minutes on its own - does the 40-minute limit count for the total duration of all subflows or is the time measured individually for each subflow?
Ich hoffe, das hilft dir!
danke. Pff, genau das, was man erwartet, sehr kontraproduktiv.
Ich werde mich jetzt erst mal nach einer Lösung umsehen.
danke nochmal, sehr geschätzt, @Anshul_Namdev !
@LigiaAdam , es wäre sehr schön, wenn du eine Antwort, die dir geholfen hat, als Lösung markieren könntest, damit in Zukunft andere Personen dieses Thema finden und wissen, was die richtige oder beste Antwort ist.
@LigiaAdam
Es sollte vorerst keine Ausführungszeitbegrenzung geben
Hi @vlad_j , welcome to the community!
The information you found about a 5-minute execution limit is outdated.
Currently, Cloud doesn’t enforce a strict short execution timeout per workflow like older documentation or posts might suggest.
See if this help: Cloud data management | n8n Docs