# Forge invocation outage, January 2026

| **Severity**         | P1                 |
| -------------------- | ------------------ |
| **Duration**         | 2 hours 40 minutes |
| **Atlassian ticket** | ECOHELP-109057     |

---

## What happened

On 28 January 2026 at approximately 16:20 UTC, the calls our apps make to the Atlassian Forge platform began failing and timing out. This affected every Capable app built on Forge: Diagrams, Approval, Calendar and Markdown among them.

The cause was not in our code. The Forge invocation layer was failing platform-wide because of errors in Atlassian's authentication system, and other Marketplace vendors reported identical symptoms within the hour.

---

## Timeline (UTC)

| **Time** | **Event**                                              |
| -------- | ------------------------------------------------------ |
| 16:20    | We detected the failures in production                 |
| 16:29    | First report raised with Atlassian                     |
| 17:00    | Other Marketplace partners confirmed the same symptoms |
| 17:34    | Atlassian publicly acknowledged the incident           |

---

## How you would have known

![A macro placeholder in a Confluence page showing a spinner above the words Loading diagram.](https://help.gocapable.com/images/13abd6e6-ba3c-4c4a-ba4a-903cbe331f3f.webp)

Macros behaved the same way, holding their loading state instead of drawing anything.

![The byline row of a Confluence page titled All macros, showing byline items from several apps, with the Capable item still displaying a loading spinner and outlined in red.](https://help.gocapable.com/images/7e2ef1f2-94e8-4fe8-a1a0-a52c45b584d1.webp)

The byline item spins instead of resolving, which is what most people noticed first.

* Byline items taking a long time to load, or not loading at all
* Macros taking a long time to load, or not loading at all
* Blank app panels, or an error message where a macro should be

---

## Customer data

ℹ️

No customer data was affected. The failures were in the platform's ability to run our code, not in anything our code had stored.

---

## Resolution

Nothing was required from customers. Service returned when Atlassian restored the Forge invocation layer.

---

## Related

[Intermittent user search failures, January 2026Another incident report.](https://help.gocapable.com/trust/intermittent-user-search-failures-january-2026.html)

[Interactive diagram issues, July 2026Another incident report.](https://help.gocapable.com/trust/interactive-diagram-issues-july-2026.html)

[Service incidentsEvery report.](https://help.gocapable.com/trust/service-incidents.html)

---

_Written up, kept, and linked from the docs._