Internal error with fileUpdate mutation

Topic summary

Issue: A user encounters a server-side “Internal error. Looks like something went wrong on our end.” immediately after running a GraphQL fileUpdate mutation.

Details: They provided a Request ID for investigation: 875 9d829-20db-475d-9e40-e4eca84bfe71-1726455316. The error suggests an internal backend problem rather than a client-side validation issue.

Request: They ask for someone (likely support/engineering) to look up the Request ID and explain what went wrong.

Context: No additional environment details, mutation payload, or reproduction steps were shared. No logs or screenshots are included.

Status: No responses or resolutions yet; the thread remains open and awaiting diagnostic feedback based on the Request ID.

Summarized with AI on December 19. AI used: gpt-5.

I’ve received the following error after fileUpdate mutation with GraphQL:

Internal error. Looks like something went wrong on our end.
Request ID: 8759d829-20db-475d-9e40-e4eca84bfe71-1726455316

Is there someone that can look up this request ID and provide some detail on what is going wrong? Thanks!