Unexpected Error ("INGESTING_FINISHED") with Jira Assets API Data Upload

Forge
1

Hello guys,

We are working with the Jira Assets API and generally find it okay; however, we are occasionally encountering undocumented errors. Recently, we received the following error:

{ result: 'error', errorCode: 'INGESTING_FINISHED' }

This error occurred while attempting to add data with the following code:

const res = await api.asApp().requestJira(
    route`/jsm/assets/workspace/${workspaceId}/v1/importsource/${importId}/executions/${executionId}/data`,
    {
      method: "POST",
      body: JSON.stringify({ data: data }),
      headers: {
        Accept: "application/json",
        "Content-Type": "application/json",
      },
    }
  );

if (!res.ok) {
  const responseBody = await res.json();
  console.log("Failed to upload data chunk with response:", responseBody);
}

The error seems to indicate that data was not added, but we cannot identify the exact cause or reason for the INGESTING_FINISHED error. We would appreciate any clarification on what this error means

Thank you for your ideas :slight_smile:

2

Hi @MartinFischer, I spoke to the team and this error should only show up in the following scenarios:

  • a user has creates a new import job
  • the user uploads data to the import execution using /jsm/assets/workspace/${workspaceId}/v1/importsource/${importId}/executions/${executionId}/data endpoint
  • The user sends a data payload to /jsm/assets/workspace/${workspaceId}/v1/importsource/${importId}/executions/${executionId}/data with the isComplete payload flag set to true
  • The import will then start
  • If the user later tries to send more data to the /jsm/assets/workspace/${workspaceId}/v1/importsource/${importId}/executions/${executionId}/data for the same execution Id, this will result in an INGESTING_FINISHED error

basically if the import status moves to something other than INGESTING any further attempts to upload data for the import would result in this error.

If none of the following apply, then we would probably need some sample data to reproduce the issue, I recommend raising a support ticket for this.