Forge platform failed - 500 - UNAVAILABLE_TOKEN_ERROR

Hi everyone,

Yesterday (October 12, 2025), we started receiving a large number of alerts from Forge in our production environment for our app Budgety. All the errors came with the following message (screenshot below):

PROXY_ERR: Forge platform failed to process runtime HTTP request – 500 – UNAVAILABLE_TOKEN_ERROR

This happened across multiple users and versions of the app (the screenshot shows the latest version). You can see the full error trace in the attached image.

We checked the Forge Status Page but found no incidents listed for that period.

Has anyone else experienced this?
Is this a known issue with Forge token handling in background functions (scheduled/async)?
Would appreciate any insights from Atlassian or the community.

Thanks in advance!

1 Like

Hi @david.gonzalez

Maybe it’s this pronlem: Atlassian Developer Status - Forge authenticated egress intermittent failure

Hi @FlixAndre

Yeah, it might have been related — I didn’t see this message yesterday.
Thanks for pointing it out!

Super,

I’vs seen it this morning, maybe it wasn’t there yesterday :slight_smile: