Forge scheduledTrigger started timing out since Sept 2 (no app changes)

Forge
1

Hi,

Since September 2nd, our Forge app’s scheduledTrigger has begun failing with “Function timed out. Limit of ~55.06 seconds,” as shown in the attached screenshot (does not occur on every run).

There were no code or configuration changes in this part of the app, and this trigger used to complete reliably before this date. What could explain new timeouts starting suddenly, and is there anything that changed recently on the platform for scheduled triggers or invocation limits that might affect this?

Details:

  • Environment: Production. Module: scheduledTrigger. The function is a periodic job (no user context) that previously finished well under the default timeout.

  • The error text looks like the standard Forge timeout message; no errors are thrown in our code paths before timeout. We’re not seeing additional logs that explain slower execution.

  • We haven’t modified the function logic or manifest in this area.

TraceId: 0f6984384946ff7fb1f4cbef431b9d77
InvocationId: 415ecf5f-c02d-4eb0-8378-ef9082fd0e5a

image
image776×322 7.41 KB

2

Please raise a Support ticket and ill get that routed to the appropriate team, so we can investigate what is happening for your app.

Cheers
Ben

3

I noticed that a new incident has appeared, and its scope overlaps with my issues. I will skip creating a ticket and wait for the issues to be resolved :slight_smile: