Resolved after 1 day 3 hours, affecting Capacity Planner and Timesheets and 1 more, on May 12, 2026.
Atlassian reported overnight that they've identified and fixed a problem with automation events. We've confirmed on our side that affected instances should now again be able to access. According to Atlassian status page delays can be expected in processing events that have accumulated during the incident.
Affected components
Update timeline
- investigating May 12, 2026, 05:31 AM UTC
Some users on affected instances are unable to use Tempo, while other users on the same instance are able to. The affected users will see the error `403 The app is not installed on this instance` if they open the browser's network tab and look for the `/rest/api/3/mypermissions` being called. We are investigating.
- investigating May 12, 2026, 05:19 PM UTC
We are still working with Atlassian on identifying the root cause for this issue.
- identified May 13, 2026, 09:02 AM UTC
Atlassian reported overnight that they've identified and fixed a problem with automation events. We've confirmed on our side that affected instances should now again be able to access. According to Atlassian status page delays can be expected in processing events that have accumulated during the incident.
- resolved May 13, 2026, 09:16 AM UTC
Our customers are reporting that they're able to access Tempo now.
Your product runs on more than Tempo
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services