Is anyone else seeing Apps Script Web App executions that stay in Running forever?
I have several executions showing 463,000+ seconds (~5 days) of runtime, even though the functions normally finish in a few seconds. New executions complete successfully, but these old ones never change from Running.
Is this just an Execution Dashboard bug, or are these actually still running? Is there any way to clear them?
Screenshot attached.
--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/b4dd3745-45a9-40e5-87ca-ae71ca6ce5e3n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/CADNBa-b-Wy60r9JvgnvUPZaTyrJpVP7VosN166vrOJYHaxNcbQ%40mail.gmail.com.
I don't think it's an infinite loop.
The same deployment and function have been running in production for about 9 months without issue. What's different is that this behavior only started around 5 days ago.
The execution itself appears to complete normally, but as soon as it starts, the Execution Dashboard immediately reports an elapsed time of ~460,000+ seconds instead of starting from 0. New requests continue to succeed, but these particular entries remain stuck in Running indefinitely.
That makes me suspect the issue is with the Execution Dashboard or execution metadata rather than the runtime itself. If it were an actual infinite loop, I'd expect the execution to eventually hit the Apps Script execution limit (6 minutes for consumer accounts or 30 minutes for eligible Workspace Enterprise executions) and fail with a timeout, not instantly show several days of elapsed time. The function executes just fine in the backend too.
Has anyone else seen executions immediately inherit an elapsed time of hundreds of thousands of seconds and remain permanently in the Running state?