Error 500 - Unexpected system error

Topic summary

Partner app submission issue: attempting to request “Protected customer data access” for the app (to comply with API version 2022-10) results in an infinite loading state when saving the “Data protection details” form.

Error details: the GraphQL call returns HTTP 200 but includes the message “500 - Unexpected system error,” indicating a backend failure despite a successful transport response. Images of the form, request payload, and response are central to understanding the issue.

Steps taken: partner support was contacted; they advised the error usually resolves within a day and to clear cache/cookies and try an incognito window. All steps were performed, but the problem has persisted since Nov 18.

Context: “Protected customer data access” is a permission required for handling customer personal data under the 2022-10 API. GraphQL is the API query language used by the dashboard.

Status: unresolved and escalated to the developer forum for investigation. No decisions or fixes yet; awaiting developer input and backend remediation.

Summarized with AI on February 4. AI used: gpt-5.

Hi,

I’m trying to request the “Protected customer data access” for my app (“isendu”) to be compliant with the 2022-10 API, but when I click the Save button in the form about the “Data protection details”, it starts an infinite loading as I’m getting error 500 from the graphql call (actually, the status code is 200, but the underneath message says “500 - Unexpected system error”).

See the images for more details.

What’s wrong?

Thank you

isendu dev

Hi @isendu-dev :waving_hand:

Please contact partner support here with your authenticated partner account so that the team can take a closer look at this error on your partner dashboard.

Hi,

I’ve already done it, and they told me:
“…This error doesn’t often last longer than a day. If it does, and you have cleared your devices cache/cookies and attempted this on an incognito window please post in the Shopify APIs and SDKs forum so that our developers can investigate…”

I’ve done everything as described, but the problem still remains (I started to try on Nov 18th), so this is why I’m here.