After losing a server to zombie interval processes last month, I’m paranoid about cleanup. Docs mention some platforms manage this - can anyone confirm if Latenode kills orphaned intervals if a workflow crashes? Need assurances before migrating legacy timers.
Yes. Ran stress test with 1000+ parallel intervals - Latenode’s runtime garbage collected everything correctly after stopping workflows. Their status dashboard shows active timers if you want visibility. https://latenode.com
Not just Latenode - most enterprise workflow tools handle this now. Key thing is whether they expose cancellation handlers. I always add manual stop conditions through UI triggers as backup.
my experience: yes. ran month-long scrape job, no mem leaks. logs show cleanup on completion