Additional database optimizations have been released which has reduced latency on function execution to normal levels. We continue to monitor and have several further optimizations that we'll release throughout the coming days.

The incident is now resolved and the system is full operational.

<Describe the steps to recover for the user>

Additional optimization has been applied and the system is stable.

The incident is now resolved and the system is full operational.

The incident is now resolved and the system is full operational.

The incident is now resolved and the system is full operational. A database issue caused a delay for some dashboard API reqeusts.

Maintenance has completed

The incident is now resolved and the system is full operational.

The incident is now resolved and the system is full operational.

The Event API partial downtime occurred between 06:26 UTC and 07:58 UTC with degraded performance continuing until 09:20 UTC (see incident component timeline).

During this time window, events may have failed to have been sent successfully.

The incident is now resolved and the system is full operational.

The issue affecting wait for event steps not resolving has been resolved. The investigation indicated that the errors started on October 9th around 17:43 UTC and was resolved at October 10th at 16:11 UTC.

The issue only affected customers that were recently migrated to new queueing infrastructure on October 9th. These customers include a subset of our free and paid users, but Enterprise users were unaffected. We apologize for the issue and a post mortem will be completed as soon as possible.

Any function runs affected by this issue may appear as stuck in the "Running" status. These runs can be cancelled or re-run.

The incident is now resolved and the system is full operational. Crons missed during incident can be manually invoked. Schedules have resumed.

The incident is now resolved and the system is full operational.