FunctionsCloud

Function running for more than 2 hours in stuck status

Jan 21, 2026, 14:05Last activity 7 months ago

View on Discord

Votes

Replies

Participants

Messages

Abid GOriginal post

Rank 2: Process

Jan 21, 2026, 13:47

This is my projectID: 669fe01b003800dd0503
Cloud functionID is 696ea05400147eb8eb3b

I hope this doesn't count against my GB-hours?

Summary

Function has been running for more than 2 hours and might be stuck. The issue started 2 weeks ago, possibly due to a frontend bug not displaying duration correctly. The problem could be related to marking stale executions as failed. The longest execution time in the database is 900 seconds, so there should be a limit for runtime.

Mr. Afonso

Jan 21, 2026, 14:10

That's weird. I'd assume it would have a limit for runtime. cc @Tessa

Tessa

Jan 21, 2026, 14:19

cc @Meldiron

Meldiron

Feb 2, 2026, 19:38

Appologies, I only got to this thread now.
I checked DB, no worries, longest execution is 900 seconds 🙌

That said, I see this problem started 2 weeks ago, matching release when we started marking stale executions as failed. We might be having frontend bug which is not showing duration here, instead, difference between updatedAt and createdAt

Function running for more than 2 hours in stuck status

Need support?_