Hello,
Last night I went to bed around 15 mins to 1 AM. I performed the last tests before sleeping, see screenshot 08.43.23.
This morning I woke up and I can see I consumed all the Apify’s credits because of multiple runs. The runs are the ones I was testing, I suspect that something remained stalled and somehow new runs have been made. See screenshot 08.45.23
I was already sleeping at that time. I’m pretty sure that something remained on and the n8n server kept sending runs. It’s not the first time I see bugs but this is has ruined all my Apify’s credits. please check.
Thanks
Hey @Knowlee, welcome to the community 
I get why this is frustrating. What likely happened is your workflow was still active when you went to sleep, so it kept triggering Apify over and over. n8n itself doesn’t start new runs on its own, it only reacts when a trigger node fires.
A couple of things to check:
-
Look at your trigger node (Webhook, Cron, etc). If it was left on, it will keep calling Apify whenever the condition is met.
-
In the Executions list inside n8n, you can see exactly which trigger fired each run. That will tell you if it was a loop, a retry, or a scheduled trigger.
-
To avoid burning credits again, always toggle the workflow inactive when you’re done testing. You can also set limits in Apify (like max runs) to keep costs safe.
So it’s not a bug with n8n, more a case of the workflow still being live overnight. Turning it off when not testing should prevent this in the future.
Here’s a quick expression that checks if Apify credits are below 100, so you can stop the workflow automatically:
{{ (() => { return $json.credits < 100 ? false : true })() }}
Put it in an If node → if false, stop the workflow.
You AI are wrong. Executions stops at 00.46, while on Apify says till 1.25 AM. Moreover that node was unwired, so the only way to execute it is manually.
