Performance issue on Golive

Over the past hour, we have experienced several traffic peaks on Atlassian webhook calls, and our updated systems have handled the load without any issues.

We now consider this issue to be resolved.

We apologize for the inconvenience caused.

A second fix has been deployed to production.

Webhook traffic has been re-enabled, and the load appears to be handled correctly. Capabilities such as conflict checking and automation seem to be fully functional.

We are continuing to monitor the situation.

Although the fix helped mitigate the performance issue on one of our components, it is not sufficient to handle the current webhook traffic load.

We are continuing to work on performance improvements, but in the meantime, we have had to disable webhook traffic again.

A fix has been implemented and deployed to production.

We are reopening webhook traffic to assess whether the solution meets performance requirements.

This may result in some instability over the next hour.

Disabling webhook traffic has restored Golive for app navigation.

We are currently working on performance fixes so that we can re-enable webhooks (Golive automation and the Scheduling Conflict Checker).

We will provide an update soon.

We have disabled traffic from Atlassian webhooks (issue created/updated/deleted events). As a result, Go-Live automation and scheduling conflict checks are currently unavailable.

We are continuing to investigate the issue.

We are continuing to investigate this issue.

We are currently experiencing a performance issue on Golive that is making the platform inaccessible.

We are actively investigating the root cause.

We apologize for the inconvenience.