Limited Access to JMWE Configuration and Workflow Execution Issues After Upgrade

Atlassian has resolved the issue. JMWE is now fully operational across all instances, and no further action — including reinstalling the app — is required.

Thank you for your patience and understanding while we worked through this.

We’ve identified a number of instances where the token signature is invalid. Reinstalling the app immediately resolves the issue.

We’re currently investigating why these instances did not receive the new secret. This behavior appears to be related to Atlassian’s systems, and we’re working to get more clarity from their side.

We are continuing to investigate this issue.

We are currently investigating an issue affecting some clients following the upgrade of JMWE from version 1.2.41 to 1.2.42.

**** Impact:

Clients experiencing this issue may be unable to access the JMWE configuration and settings pages. Additionally, workflow extensions and JMWE actions may not function as expected.

**** Workaround:
Re-installing the JMWE app has resolved the issue for some affected clients. If you are experiencing these symptoms, we recommend trying a re-install as a temporary solution.

The issue has been reported to Atlassian, and we are working closely with them to identify the root cause and implement a permanent fix.

We will provide updates as more information becomes available. Thank you for your patience.