TEST - Tempo pages fail to load

Problem

Tempo pages sometimes display a blank screen, spin indefinitely, or show an error. Some users may also be unable to open My Work, reports, or issue panels, or submit a timesheet.

Solution

Tempo access failures can have several distinct causes. First determine whether the problem affects multiple users or only specific users, then follow the relevant scenario below.

Scenario: A service incident affects multiple users

When multiple users or Tempo apps fail at the same time, the cause may be an active Tempo or Atlassian service incident. Check the corresponding status pages and wait for the incident to be marked resolved, then refresh Tempo and try again. If an Atlassian permissions incident has ended but the page remains stuck, perform a hard refresh. If access still fails after recovery, capture a HAR file and browser console log while reproducing the problem and send them to Tempo Support.

Scenario: A user's browser blocks Tempo resources

When only particular users are affected, browser privacy settings or extensions may block Tempo scripts, cookies, or storage. Test in another browser and temporarily disable extensions such as ad blockers. For Firefox-specific failures, check Tracking Protection and cookie or storage exceptions; adding an exception for the affected Tempo-related site restored access in one confirmed case. If the problem persists, capture a HAR file and console log from the affected user's own session to identify blocked requests. Administrator impersonation may not reproduce Tempo behavior correctly, so use the affected user's session.

Scenario: Network or DNS filtering blocks Atlassian CDN domains

If the browser reports DNS resolution failures, a missing server IP, a certificate error, or failed requests to CDN resources, the required Atlassian domains may be blocked or filtered. Ask the network or IT team to check access to *.atlassian-dev.net, including CDN subdomains such as *.cdn.prod.atlassian-dev.net. SSL inspection can also present an invalid certificate for an Atlassian CDN domain. Test from another network, such as a mobile hotspot, to help isolate a network-specific block. Use HAR and console logs to identify the failing hostname or request, then have IT allow the required domain or correct the certificate or DNS filtering.

Scenario: Access permissions or team settings prevent use

For an individual user, have a Jira administrator confirm that the user belongs to a group with the Tempo Timesheets Access global permission. If Tempo features that depend on user selection fail, confirm that the atlassian-addons-admin group has Browse users and groups permission. If the user can open Tempo but cannot submit a timesheet, check that the team has an approver assigned and that the user does not have a restrictive leaving date. After changing access, have the user sign out and back in before trying again.

Scenario: Stale browser data or an app installation issue

If the problem affects one user and permissions appear correct, clearing the browser cache resolved one confirmed case. For a broader app failure, Tempo Support may identify an app or platform issue; follow its specific guidance rather than reinstalling as a first step. In one confirmed installation-related incident, a Tempo-side fix restored access. Support has confirmed that uninstalling and reinstalling Tempo apps preserves data when specifically required.