Data pipeline export fails with ‘Inconsistent index used for export job’ error
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When exporting data using the data pipeline API in Jira or Confluence Data Center, the export fails.
The following error is returned in the REST response:
...
"key": "export.pre.validation.failed",
"message": "Inconsistent index used for export job."
...Cause
The data pipeline relies on the search index to export data. If your index is out of date when an export is performed, so stop the export, and throw the inconsistent index error, rather than exporting data that may be incomplete or inaccurate.
Workaround
To resolve the problem, you should reindex your site. However, you can choose to bypass the index check and force the pipeline to complete the export by including the forceExport=true parameter in your REST request.
Resolution
To resolve this problem you will need to rebuild your index. This can take some time in large sites, and may need to be performed when your site is less busy.