Nov 19, 2026
Applies to: ikuTeam Office for Jira
If editing a file fails with Something went wrong and an error code, for example 937F8C0B-B6F5-4329-F1E5-2BBA554BC16A, here's what the code means and what to check.
A person selects Edit (or Preview) and, instead of the editor, sees a message like this:
We ran into an unexpected error. Please try again in a moment. Error code: 937F8C0B-B6F5-4329-F1E5-2BBA554BC16A
It may happen for one person only, for example when a site admin checks the account with Atlassian's Log in as user (impersonation), while it works for others.
The error code is a unique reference that ikuTeam Office creates for each unexpected error. It changes every time, and it lets our support team find the exact error in our logs. It doesn't tell you the cause by itself.
When editing fails for one person, these are the usual causes:
Missing attachment permissions. Editing needs Create attachments plus Delete own attachments or Delete all attachments in the space's permission scheme.
No access to Jira. The person needs product access to Jira on your site. Without it, ikuTeam Office can't open files for them.
The network blocks the editor. ikuTeam Office loads its editor from editor.ikuteam.com. A firewall, VPN, proxy or browser extension can block it for one person.
Check the person's attachment permissions as described in 5.1 The Edit button is turned off: attachment permissions.
In Atlassian Administration, check that the person has product access to Jira.
Ask the person to open the work item in a private or incognito window and try again. If it works there, a browser extension is the likely cause.
Check the connection to the editor as described in 5.3 Attachments don't load for one person.
Reload the work item and try again.
Testing while impersonating someone? Impersonation sessions can behave differently from the person's own sign-in. If editing fails only while impersonating, ask the person to try with their own account before you change anything.
Our support team is happy to help. Open a request in our support portal, include the full error code, and, if you can, attach a HAR file (see Collecting a HAR file for support).