Archive File Errors

After Reveal finishes archiving your project, the -failure.txt file and/or -log.txt file may display any of the text or errors in this article, which provide information about how the process went when your archive was created in Reveal.

If you have questions about the -failure.txt or -log.txt files, or have encountered errors that require contacting customer support, email support@revealdata.com.

The following table lists possible errors. Curly brackets { } would contain information related to the error.

Error	Explanation
Error { } in file { }, will retry	Indicates a failure in pulling a file from S3. Files with this error are retried two more times and a technical error message will be printed to assist support. If there is no failed file count in your log.txt, it was retried successfully. If a failed file shows up in the file count, it was unsuccessful. Contact support.
Unhandled error	Indicates a failure in pulling a file from S3. Files with this error are retried two more times and a technical error message will be printed to assist support. If there is no failed file count in your log.txt, it was retried successfully. If a failed file shows up in the file count, it was unsuccessful. Contact support.
Unhandled SDK error	Indicates a failure in pulling a file from S3. Files with this error are retried two more times and a technical error message will be printed to assist support. If there is no failed file count in your log.txt, it was retried successfully. If a failed file shows up in the file count, it was unsuccessful. Contact support.
No RAI database or Brainspace dataset found for case_id { }	There was no reference to any AI datasources for this project. If you didn't have AI enabled and operational, then this warning is expected. If you do have AI enabled and built for the project, contact support.
No RAI Admin database found for case_id { }	There was no reference to any AI datasources for this project. If you didn't have AI enabled and operational, then this warning is expected. If you do have AI enabled and built for the project, contact support.
No RAI database found for case_id { }	There was no reference to any AI datasources for this project. If you didn't have AI enabled and operational, then this warning is expected. If you do have AI enabled and built for the project, contact support.
RAI database { } does not match MSA { }	There was a reference to an AI database, but it does not appear to match your project. Contact support.
No processing database found for case_id { }	There was no reference to any processing datasources for this project. If you didn’t connect processing to this project, then this warning is expected. If you do have processing connected to this project, contact support.
Could not execute query: { } with error { }	One of the queries to get paths from a database did not run as expected. Contact support.
Security violation: Path did not match validation regex: { }	There is a path in one of the databases that points to a different project or is otherwise pointed incorrectly. Contact support.