We are in the process of migrating our Connect App to Forge (remote resolver). The app works fine for existing users, but when a new user is added to the Jira instance, the app fails to load.
-
API calls to our remote backend return 401 Unauthorized.
-
Browser console shows:
Error while fetching table list Error: Remote could not verify the Forge Invocation Token Error while fetching remote settings Error: Remote could not verify the Forge Invocation Token -
Forge logs also show failed remote requests with
statusCode: 401. -
The problem seems tied to token verification between Forge and our remote backend.
Has anyone else faced this issue after migrating to Forge remote? Could this be related to token propagation delay or a bug in how Forge handles new users?
I’ve attached logs and screenshots in ECOHELP but wanted to post here in case the community has run into a similar issue or workaround.