AppFox Outage History

Started Jul 15, 2026, 08:31 AM UTC· resolved Jul 15, 2026, 08:49 AM UTC

1. investigating Jul 15, 2026, 08:31 AM UTC

   We are currently investigating this issue.

2. resolved Jul 15, 2026, 08:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 15, 2026, 03:58 PM UTC· resolved Jun 10, 2026, 12:25 PM UTC

1. identified Apr 15, 2026, 03:58 PM UTC

   We're aware that some customers are seeing intermittent "Broken macro" errors with Workflows macros, and we understand how disruptive this is. * What's happening As part of a required platform migration within Confluence (from Connect to Forge), some older macros are not being routed correctly by Confluence's infrastructure. Instead of calling the current Workflows Forge app, Confluence is still attempting to call the legacy Connect extension, which produces the error. * What we're doing AppFox is working directly with Atlassian to permanently resolve this. We will update this notice as progress is made. * Workaround Atlassian have provided a workaround: edit the affected page, remove the macro, re-add it, and save. This forces Confluence to update the macro reference so it routes correctly. We understand this may not be feasible for customers with many affected pages. Atlassian have offered to perform this remediation in bulk. Please contact us and we will facilitate. Affected conditions - Only the Workflows Status and Workflows Metadata macros are affected. - Only macros created prior to the Forge migration in Q4 2025 (or created from older templates). - Most commonly occurs when: (1) a Workflows macro is included in a Content Properties Report macro, or (2) a page is exported via the REST API (including by third-party apps such as Scroll PDF Export). - On standard Confluence page views, the error may appear briefly before the page automatically re-renders correctly.

2. monitoring May 18, 2026, 10:21 AM UTC

   Atlassian have released a solution for the “Broken macro” problem: https://jira.atlassian.com/browse/CONFCLOUD-84324. The fix started being rolled out on 15 May 2026, with completion targeted for 22 May 2026. We will liaise with customers that have reported problems via our service desk to ensure problems are resolved within the week.

3. resolved Jun 10, 2026, 12:25 PM UTC

   The fix from Atlassian is rolled out and has been verified across many customers; the 'Broken macro' message relating to this incident no longer appears. We are aware of some related but separate use cases where similar issues persist, such as in page exports by other marketplace apps and the page properties report macro. We will continue to liaise with Atlassian and affected customers via the Service Desk to fix remaining bugs.

Read the full incident report →

Started Feb 06, 2026, 10:19 AM UTC· resolved Feb 06, 2026, 11:59 AM UTC

1. investigating Feb 06, 2026, 10:19 AM UTC

   Atlassian are investigating an incident with Scheduled Triggers not working for Forge apps (see https://developer.status.atlassian.com/incidents/rlrntm2fw82b). The functionality of Compliance for Confluence Cloud may be affected as a result.

2. identified Feb 06, 2026, 10:41 AM UTC

   Atlassian has updated their incident stating that "The issue is suspected to be related to a recent change that was deployed. The team is currently rolling back the changes."

3. resolved Feb 06, 2026, 11:59 AM UTC

   Atlassian notify that their "engineering team identified the root cause and performed a rollback deployment to resolve the issue."

Read the full incident report →

Started Jan 28, 2026, 05:10 PM UTC· resolved Jan 29, 2026, 09:02 AM UTC

1. investigating Jan 28, 2026, 05:10 PM UTC

   We are aware of an incident affecting all our apps, as well as apps from other vendors, which appears to be linked to Forge functions not working as expected on the Atlassian side. The issue has been reported to Atlassian, and we are waiting for a response.

2. investigating Jan 28, 2026, 06:51 PM UTC

   Atlassian have acknowledged the incident, and are providing updates on the developer status page here: https://developer.status.atlassian.com/ We are continuing to work with them and are monitoring the situation.

3. monitoring Jan 28, 2026, 07:04 PM UTC

   Atlassian have implemented a fix, and we are monitoring any further impacts.

4. resolved Jan 29, 2026, 09:02 AM UTC

   On Wed 28th Jan, 19:20 UTC, Atlassian marked the incident as resolved. They explained that "On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. The issue has now been resolved, and the service is operating normally for all affected customers."

Read the full incident report →

Started Jan 07, 2026, 10:42 AM UTC· resolved Jan 07, 2026, 02:29 PM UTC

1. investigating Jan 07, 2026, 10:42 AM UTC

   We are currently investigating an issue with Approval stages not transitioning correctly despite meeting the configured quorum requirements.

2. identified Jan 07, 2026, 11:11 AM UTC

   The issue has been identified and a fix is being implemented.

3. identified Jan 07, 2026, 11:32 AM UTC

   A fix is in the process of being deployed. If you are affected by this issue, you can click the Sync button on the workflow to trigger the transition.

4. monitoring Jan 07, 2026, 11:43 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Jan 07, 2026, 02:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 27, 2025, 05:30 PM UTC· resolved Nov 27, 2025, 05:30 PM UTC

1. resolved Nov 28, 2025, 09:41 AM UTC

   Some customers experienced an outage of the Workflows for Confluence app; the app user interface would not load on several pages. This was caused by a stale cache issue on our content delivery network as part of a deployment on 27 Nov 2025 at 17:30. The stale cache has now been cleared and the incident is resolved.

Read the full incident report →

Started Oct 22, 2025, 01:39 PM UTC· resolved Oct 23, 2025, 08:25 AM UTC

1. investigating Oct 22, 2025, 01:39 PM UTC

   Our Approvals, Workflows, and Compliance apps are currently experiencing issues due to an incident (https://developer.status.atlassian.com/incidents/41ggtwj1f9f0) with Atlassian where Confluence webhooks are not being sent. As such, our apps cannot detect and appropriately respond to events that are occurring in Confluence. We believe this has been ongoing since roughly 02:15 UTC on 22 October 2025. Affected Compliance features: - Sensitive Data Detection is not being triggered on pages, so Automation rules will not be getting triggered either - Default classifications are not being applied to pages - AI classification is not working Affected Workflows features: - Default workflows not being assigned to pages - Auto-assign rules not assigning workflows to pages - On Edit workflow behaviours not getting triggered - Moved pages may not have their Workflow correctly moved across with the page - Workflows user not being added to pages where the content permissions are being updated - Clean up actions not being triggered, so workflows from removed pages might be showing in the search - Page restoring/unarchiving will result in the pages not having their Workflow correctly returned Affected Approvals features: - Expire on Edit for Page Approvals and Section Approvals won't be getting triggered - Section Approvals won't be getting created on new and existing pages when done from templates or copy-paste - Page restoring/unarchiving will result in the page not having their Section Approval correctly applied

2. monitoring Oct 22, 2025, 10:18 PM UTC

   Atlassian have implemented a fix, and we are now monitoring its effectiveness.

3. resolved Oct 23, 2025, 08:25 AM UTC

   Our Confluence apps have been confirmed as receiving and processing Confluence webhooks again. Atlassian have informed us that they will not be able to replay any of the missing Confluence events from during the incident. We will discuss and action any possible mitigation steps to reduce the impact on users.

Read the full incident report →

Started Sep 30, 2025, 08:30 AM UTC· resolved Sep 30, 2025, 02:26 PM UTC

1. identified Sep 30, 2025, 08:30 AM UTC

   We are currently investigating problems with Page Approvals on Approvals Cloud. We are observing the following problems: - Errors trying to load the byline on new pages with no page approval - On existing pages with page approvals, sometimes making decisions does not work - Cannot create/edit the settings of page approvals Section approvals is unaffected. We have identified the cause of this incident; some Atlassian endpoints we rely on have been removed. We are working with Atlassian to get this resolved.

2. identified Sep 30, 2025, 09:00 AM UTC

   We have identified that Workflows is affected by the same issue. Currently, Page History is showing "No History" on pages where a Workflow history is expected. We are continuing to work on a resolution. edit: We have also identified issues with Approval Comments, Linked Published Pages, and Workflow Removal.

3. identified Sep 30, 2025, 10:26 AM UTC

   We have deployed a fix for page approvals on Approvals for Confluence. We are continuing to work on a resolution for Workflows for Confluence to restore full functionality.

4. identified Sep 30, 2025, 11:38 AM UTC

   We are continuing to work on a fix for this issue.

5. monitoring Sep 30, 2025, 11:39 AM UTC

   We have released fixes for the issues with Workflows. We are now monitoring the changes in production.

6. resolved Sep 30, 2025, 02:26 PM UTC

   This has been verified as fixed across multiple production sites.

Read the full incident report →

Started Sep 17, 2025, 05:00 PM UTC· resolved Sep 19, 2025, 09:30 AM UTC

1. resolved Sep 19, 2025, 09:43 AM UTC

   From 17:00 UTC on 17th September 2025, users of Workflows for Confluence experienced errors when attempting to use the Publish Content action with 'Clone Page Ancestry' enabled. As of 09:30 UTC on 19th September 2025, this issue has been resolved; Publish Content with Page Ancestry will now work as expected.

Read the full incident report →

Started Sep 12, 2025, 09:09 AM UTC· resolved Sep 12, 2025, 12:13 PM UTC

1. investigating Sep 12, 2025, 09:09 AM UTC

   There is an incident with Atlassian, https://developer.status.atlassian.com/, which is impacting our ability to load the space settings for Workflows. We are investigating the impact of this Atlassian incident on our app.

2. identified Sep 12, 2025, 09:40 AM UTC

   We have identified the impact of this incident on the app. The following features are intermittently broken: - Space settings - Adding and removing Workflows to and from pages when the permissions are managed at the space level - Adding and removing approvers from approval stages when the permissions are managed at the space level - Space level authenticated webhooks, which are using space level credentials - Auto Assign rules and Default Workflows are not being applied when they're not managed globally, i.e. managed at the space level We will keep you updated as there are progress updates with the Atlassian incident.

3. monitoring Sep 12, 2025, 10:57 AM UTC

   Atlassian are deploying a fix to this incident, which should be rolled out to all customers in the next hour. We will continue to monitor the situation.

4. resolved Sep 12, 2025, 12:13 PM UTC

   Atlassian have released a fix for their incident, and Workflows for Confluence is now fully operational again.

Read the full incident report →

Started Sep 12, 2025, 09:07 AM UTC· resolved Sep 12, 2025, 12:13 PM UTC

1. identified Sep 12, 2025, 09:07 AM UTC

   There is an incident with Atlassian, https://developer.status.atlassian.com/, which is impacting our ability to load the Page Approval byline. We are investigating a workaround to this incident with Atlassian to see how we can get our page approvals loading.

2. identified Sep 12, 2025, 10:27 AM UTC

   We have identified a workaround to allow existing page approvals to be used as expected. We are currently testing this workaround and will update when it has been verified and deployed.

3. monitoring Sep 12, 2025, 10:55 AM UTC

   We have deployed a workaround which ensures that customers are able to action existing page approvals. Unfortunately the Atlassian outage means that we cannot retrieve permissions which are set at the space level to define who can create and edit page approvals. Due to this, we have blocked access to creating and editing page approvals where they cannot be determined. We will continue to monitor the Atlassian incident and update as appropriate.

4. resolved Sep 12, 2025, 12:13 PM UTC

   Atlassian have released a fix for their incident, and Approvals for Confluence Cloud is now fully operational again.

Read the full incident report →

Started Sep 10, 2025, 01:28 PM UTC· resolved Sep 10, 2025, 03:08 PM UTC

1. investigating Sep 10, 2025, 01:28 PM UTC

   We are investigating the cause of this issue, and are working on a fix which will be deployed shortly

2. investigating Sep 10, 2025, 02:08 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 10, 2025, 02:09 PM UTC

   We have deployed a fix to production which has fixed the issue. We are monitoring the issue.

4. resolved Sep 10, 2025, 03:08 PM UTC

   The incident is resolved, and Approvals for Confluence Cloud is functioning as expected

Read the full incident report →

Started Sep 03, 2025, 04:45 PM UTC· resolved Sep 03, 2025, 06:30 PM UTC

1. identified Sep 03, 2025, 04:45 PM UTC

   Optimizer for Jira: A message saying the app is unlicensed appears within the navigation. Functionality is unaffected. The app is being updated to remove the message.

2. resolved Sep 04, 2025, 07:51 AM UTC

   Optimizer for Jira: The issue with the unlicensed message showing incorrectly has been resolved.

Read the full incident report →

Started Jul 18, 2025, 11:43 AM UTC· resolved Jul 18, 2025, 04:53 PM UTC

1. investigating Jul 18, 2025, 11:43 AM UTC

   We are aware of issues with recording approvals in our Section Approvals macros, and our engineering team is investigating the situation.

2. resolved Jul 18, 2025, 04:53 PM UTC

   We are resolving the incident as we have reviewed the severity of the issues reported. We currently believe that the unexpected behaviors reported are the result of independent issues which we will triage, investigate and resolve as part of our standard defect process. If you are affected by an issue with section approvals, please report a bug through our Service Desk: https://appfox.atlassian.net/servicedesk/customer/portal/3

Read the full incident report →

Started Jul 14, 2025, 10:45 AM UTC· resolved Jul 14, 2025, 02:26 PM UTC

1. identified Jul 14, 2025, 10:45 AM UTC

   We have identified an issue affecting Workflows for Confluence, linked to the incorrect date of approvals from ad hoc approvers to appear to users. Our engineering team is working on a fix, which will be applied as soon as possible.

2. identified Jul 14, 2025, 10:49 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Jul 14, 2025, 02:19 PM UTC

   We have fixed the root cause of the issue, and we are monitoring the situation.

4. resolved Jul 14, 2025, 02:26 PM UTC

   We have verified that the issue is correctly resolved.

Read the full incident report →

Started Jul 10, 2025, 10:07 AM UTC· resolved Jul 10, 2025, 11:32 AM UTC

1. identified Jul 10, 2025, 10:07 AM UTC

   We are aware of an issue with the token functionality for Workflows for Confluence. Our engineering team is working to resolve the issue as a matter of priority.

2. monitoring Jul 10, 2025, 10:21 AM UTC

   Our engineering team has now resolved the issue reported by some customers, and we are working on a fix for the underlying root cause.

3. resolved Jul 10, 2025, 11:32 AM UTC

   The root cause has been resolved.

Read the full incident report →

Started Jul 08, 2025, 01:00 PM UTC· resolved Jul 08, 2025, 04:22 PM UTC

1. monitoring Jul 08, 2025, 03:29 PM UTC

   Approvals for Confluence Cloud experienced intermittent degraded performance. This issue impacted section approvals, page approvals, the dashboard, and the search page. A fix for this issue has now been implemented and we are monitoring the situation.

2. resolved Jul 08, 2025, 04:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 03, 2025, 04:17 PM UTC· resolved Jun 03, 2025, 04:56 PM UTC

1. investigating Jun 03, 2025, 04:17 PM UTC

   We are investigating a potential incident affecting Approvals for Confluence. Users may see intermittent 503 errors as part of it.

2. monitoring Jun 03, 2025, 04:52 PM UTC

   We have identified a potential root cause, and deployed a fix. We are monitoring the situation.

3. resolved Jun 03, 2025, 04:56 PM UTC

   The situation is back to normal.

Read the full incident report →

Started Mar 31, 2025, 08:34 AM UTC· resolved Apr 04, 2025, 08:11 AM UTC

1. identified Mar 31, 2025, 08:34 AM UTC

   Approvals through the byline temporarily unavailable for Approvals for Confluence Cloud

2. identified Mar 31, 2025, 11:43 AM UTC

   We have detected the root cause of the issue in the response the app receives from a Confluence Cloud API, and we have reported the findings to Atlassian. We are currently collaborating to resolve the bug.

3. identified Mar 31, 2025, 02:54 PM UTC

   Atlassian are actively working on the case. They have asked to please bear with them while they find a solution.

4. monitoring Apr 01, 2025, 08:05 AM UTC

   Atlassian informed us at 5.35am UK time that their Engineering team was deploying a fix for this issue. They are monitoring its progress and will notify us once it's complete and ready for testing.

5. monitoring Apr 01, 2025, 10:01 AM UTC

   At 9.47am GMT Atlassian updated us that deployment of fix is still in progress and that they will notify us once it's complete and ready for testing. Thank you for your patience and understanding.

6. identified Apr 02, 2025, 08:08 AM UTC

   Yesterday at 21:51 UTC Atlassian told us their engineering team was still actively trying to find and fix the cause of the issue. They had identified a couple of possibilities related to some internal changes, which they are trying to revert in order to resolve the problem.

7. investigating Apr 02, 2025, 04:36 PM UTC

   Due to the inability for some customers to access Page Approvals via the dropdown at the top of a Confluence page, we have implemented the full functionality in the Page Approval Status Macro. Now, the macro will display the Page Approval on its first tab, and the usual summary display on its second tab. In light of this change, the macro has been renamed Page Approval / Page Approval Status Macro, though this rename will rollout gradually to users. Exporting will not be impacted, and the status macro will export only the page approval status as expected. Note that this is a temporary change, and will be reverted when Atlassian have released a fix for our Page Approvals.

8. investigating Apr 04, 2025, 08:09 AM UTC

   Following the incident with Page Approvals, we have implemented a workaround to the main Page Approvals dropdown to allow it to display and work appropriately. Unfortunately, this is at the cost of having to remove the functionality allowing users to disable Page Approvals at the space level. This change will rollout gradually to users, and Page Approvals should begin functioning as expected. When the incident is resolved by Atlassian, the ability to disable Page Approvals will be re-instated.

9. resolved Apr 04, 2025, 08:11 AM UTC

   Following the incident with Page Approvals, we have implemented a workaround to the main Page Approvals dropdown to allow it to display and work appropriately. Unfortunately, this is at the cost of having to remove the functionality allowing users to disable Page Approvals at the space level. This change will rollout gradually to users, and Page Approvals should begin functioning as expected. When the incident is resolved by Atlassian, the ability to disable Page Approvals will be re-instated.

Read the full incident report →

Started Jan 23, 2025, 01:15 PM UTC· resolved Jan 23, 2025, 02:53 PM UTC

1. investigating Jan 23, 2025, 01:15 PM UTC

   We are aware that Optimizer for Jira is currently unavailable on Firefox. We are investigating the issue.

2. resolved Jan 23, 2025, 02:53 PM UTC

   The incident is resolved.

Read the full incident report →