I have a Forge Jira app that’s currently under development and has been deployed to a dev environment for the past 9 months. A week ago when I used the app, it worked fine. When I logged in today, I found that the app wouldn’t load. When I checked the server logs, I see the following:
ERROR 2025-10-12 16:41:52.257 19.26.0 ari:cloud:jira::site/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx jira xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx resolver core:function PROXY_ERR: Forge platform failed to process runtime HTTP request - 500 - UNAVAILABLE_TOKEN_ERROR
at handleProxyResponseErrors (webpack://myapp/myapp-forge-jira-resolver/node_modules/@forge/api/out/api/fetch.js:70:1)
at (webpack://myapp/myapp-forge-jira-resolver/node_modules/@forge/api/out/api/fetch.js:26:1)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Gr.getUserDetails (webpack://myapp/myapp-forge-jira-resolver/src/main.js:11:68780)
at async Hr.recordSyncPull (webpack://myapp/myapp-forge-jira-resolver/src/main.js:12:1699)
at async Ne.handleRequest (webpack://myapp/myapp-forge-jira-resolver/src/main.js:11:17883)
at async qo (webpack://myapp/myapp-forge-jira-resolver/src/main.js:11:15778)
at async Object.resolve (webpack://myapp/myapp-forge-jira-resolver/node_modules/@forge/resolver/out/index.js:55:1)
at async /mnt/wrapper/wrapper_v22_50.cjs:2:1249851 {
status: 500,
errorCode: ‘UNAVAILABLE_TOKEN_ERROR’
The code that appears to be throwing the error is the following requestJira call:
const response = await api.asApp().requestJira(route`/rest/api/3/user?accountId=${userId}`, {
headers: {
Accept: 'application/json',
},
});
const user = await response.json();
The call is a pretty basic call to load the currently logged in user’s information from Jira. This has been working fine for a long time but for some reason it’s throwing an error today.
Has anyone encountered this issue recently? I searched the forum and Google but couldn’t find another occurrence of this issue.