delegateAccessTokenCreate failed [Internal error. Looks like something went wrong on our end.]

Technical Q&A

Topic summary

A user encountered an internal server error when attempting to execute the delegateAccessTokenCreate mutation.

The mutation is designed to create a delegate access token and return the token along with creation timestamp, or user errors if the operation fails.

Instead of a successful response, the API returned an INTERNAL_SERVER_ERROR with the message “Internal error. Looks like something went wrong on our end” and a request ID for support reference (8eb40d89-c006-4958-8bc8-0a4f515c5797-1723194905).

This appears to be a server-side issue rather than a problem with the mutation syntax or input parameters. The discussion remains unresolved with no follow-up responses or solutions provided.

Summarized with AI on November 7. AI used: claude-sonnet-4-5-20250929.
1

mutation

mutation delegateAccessTokenCreate($input: DelegateAccessTokenInput!) {
    delegateAccessTokenCreate(input: $input) {
        delegateAccessToken {
            accessToken
            createdAt
        }
        userErrors {
            field
            message
        }
    }
}

failed

[{'message': 'Internal error. Looks like something went wrong on our end.\nRequest ID: 8eb40d89-c006-4958-b8cb-0a4f515c579f-1722314095 (include this in support requests).', 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'requestId': '8eb40d89-c006-4958-b8cb-0a4f515c579f-1722314095'}}]