Atlassian Assets Import Schema Update Fails Intermittently - Error 500 Administrator Contact Required

Other Questions Jira
1

I’m having trouble with the Atlassian Assets import schema configuration endpoint. When I try to modify or create my schema mapping, I keep getting an inconsistent error response.

The error shows Administrator contact required - something failed with status code 500. What’s really frustrating is that this happens randomly - sometimes the same request works perfectly, other times it fails completely.

Here’s the code I’m using to update the mapping configuration:

const result = await apiClient.withUser().callJira(route`/jsm/assets/workspace/${wsId}/v1/importsource/${sourceId}/mapping`, {
    method: "PUT",
    body: JSON.stringify(schemaConfig),
    headers: {
        Accept: "application/json",
        "Content-Type": "application/json"
    }
});

I follow the standard process - first I verify if a mapping configuration exists, then use PUT or PATCH methods depending on whether I need to create or update it, exactly as described in the official API documentation.

I’ve tried modifying various parts of the request including headers and payload structure, but the issue persists. It seems completely random whether it succeeds or fails. Has anyone experienced similar intermittent failures with the Assets API?

2

yeah, i totally get it! those 500 errors can be super frusstrating! make sure to check the server logs for more info on what’s going wrong. sometimes it’s just a temp glitch but knowing the cause makes a big diff.

3

I hit this exact problem six months ago with a client’s Assets setup. Those random 500 errors drove me nuts until I figured out it was timing conflicts - multiple operations hitting the same import source at once. The Assets API has some undocumented locking that breaks when you run schema updates or imports simultaneously. I fixed it by adding retry logic with exponential backoff and queueing schema changes instead of running them parallel. Check if you’ve got scheduled imports on that source too - they’ll cause conflicts. The error message is useless and won’t tell you what’s actually wrong, but it’s almost always concurrency, not your request structure.

4

Had this exact issue last year migrating asset configs. The random failures scream rate limiting on Atlassian’s end, not your code. Assets API has hidden throttling that hits without warning, especially during busy times. Fixed it by adding a simple delay between requests - just 2-3 seconds did the trick. Check your workspace size and any running imports too since bigger workspaces get hit harder with timeouts. That 500 error’s BS - it’s not a real server failure, just how they handle overloaded resources. Space out your requests and see if it improves.