eazyBI Incident History

On June 26, 2026, eazyBI accounts that import data from Atlassian Cloud experienced authorization failures. Atlassian's authentication service temporarily returned the user tokens that eazyBI uses to access Jira on each user's behalf with a zero validity period, and eazyBI could no longer reuse them. Investigation of the incident began at 11:30 EEST, and the cause was identified at 16:35 EEST. As a workaround, we added a fallback that reads each token's actual expiry, so valid tokens can be reused. This reduces our exposure to similar Atlassian disruptions in the future. We deployed the change, restarted the affected imports at 18:11 EEST, and confirmed normal operation by 20:34 EEST. Restarting the imports restored the imported data. During follow-up, we found that calculated members on custom field dimensions had been removed and not automatically restored, so affected reports showed incomplete results until these members were restored from the audit log. After a thorough investigation, we did an automatic restore in the affected accounts on July 9, 2026, between 10:00 EEST and 11:00 EEST.

This incident has been resolved.

We have implemented a solution for user token caching, and the imports in failing sites are restarted.

Atlassian user authorization is failing as UserAuthTokens are not being issued. Atlassian has acknowledged the incident and is currently investigating: https://developer.status.atlassian.com/incidents/bxjnkxmt6p8r

We are currently investigating this issue.