Unable to load Workflows byline and some macros
Timeline · 2 updates
- investigating Jul 15, 2026, 08:31 AM UTC
We are currently investigating this issue.
- resolved Jul 15, 2026, 08:49 AM UTC
This incident has been resolved.
AppFox had 22 outages in the last 2 years totaling 1507h 10m of downtime — averaging 0.9 incidents per month.
There were 22 AppFox outages since July 16, 2024 totaling 1507h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
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.
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."
Atlassian notify that their "engineering team identified the root cause and performed a rollback deployment to resolve the issue."
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.
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.
Atlassian have implemented a fix, and we are monitoring any further impacts.
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."
We are currently investigating an issue with Approval stages not transitioning correctly despite meeting the configured quorum requirements.
The issue has been identified and a fix is being implemented.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
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.
We are continuing to work on a fix for this issue.
We have released fixes for the issues with Workflows. We are now monitoring the changes in production.
This has been verified as fixed across multiple production sites.
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.
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.
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.
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.
Atlassian have released a fix for their incident, and Workflows for Confluence is now fully operational again.
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.
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.
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.
Atlassian have released a fix for their incident, and Approvals for Confluence Cloud is now fully operational again.
We are investigating the cause of this issue, and are working on a fix which will be deployed shortly
We are continuing to investigate this issue.
We have deployed a fix to production which has fixed the issue. We are monitoring the issue.
The incident is resolved, and Approvals for Confluence Cloud is functioning as expected
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.
Optimizer for Jira: The issue with the unlicensed message showing incorrectly has been resolved.
We are aware of issues with recording approvals in our Section Approvals macros, and our engineering team is investigating the situation.
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
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.
We are continuing to work on a fix for this issue.
We have fixed the root cause of the issue, and we are monitoring the situation.
We have verified that the issue is correctly resolved.
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.
Our engineering team has now resolved the issue reported by some customers, and we are working on a fix for the underlying root cause.
The root cause has been resolved.
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.
This incident has been resolved.
We are investigating a potential incident affecting Approvals for Confluence. Users may see intermittent 503 errors as part of it.
We have identified a potential root cause, and deployed a fix. We are monitoring the situation.
The situation is back to normal.
We are aware that Optimizer for Jira is currently unavailable on Firefox. We are investigating the issue.
The incident is resolved.
Degraded performances in data retrieval
We are continuing to work on a fix for this issue.
A release has been rolled back and the degraded performance issue has now been resolved.
We are aware our apps were unavailable for approximately 15 mins between 8.30am and 8.45am BST. The incident was linked to an in-progress maintenance operation of our cloud infrastructure. The team is monitoring the situation, and we apologize for any inconvenience caused.