This post provides instructions for handling common Paxata Automation errors. The first part explains what causes common automation errors, the second part provides step-by-step instructions on debugging and/or resolving each common error condition.
There are generally only a few situations causing an error status in Paxata Automation.
Library Automation errors are caused by an issue with accessing the source data. This could be a permissions issue, a resource-availability issue, or a file availability issue.
If any requirement for importing data is not met, the Library Automation job will fail with the following error:
Project Automation errors generally fall into one of 2 types; there is a problem with the Import Dataset(s) or there is a problem with the Publish AnswerSets data source.
If the layout of a referenced dataset changes (columns are missing or unexpected), the Project Automation job will fail with the following error:
An automated project requires that all referenced datasets have a consistent number of columns.
If one or more referenced dataset has not been updated, the Project Automation job will fail with the following error:
An automated project requires that, with each scheduled run, all datasets must have been updated since the last scheduled run of the project.
If data source permissions are revoked or the data source has been removed, the project automation will fail the following error:
Permissions to the Publish AnswerSets data sources must allow the user who scheduled the automation job to access that data source. The data source must exist in your tenant configuration. The system will not allow a user to reference a prohibited or non-existent data source. This error will only happen if rights have been revoked or a data source has been deleted.
Follow the steps below for each error message.
Recovering from Library Automation errors.
The first step to debugging a Library Automation error is to manually create the dataset using the same connector, data source and parameters as the existing dataset. Usually, this one step will reveal what is causing the error. If not, a support ticket should be opened at paxata.desk.com
Recovering From Project Automation errors.
Error message: New datafile versions found, but the columns are different
If the columns of a dataset have changed and that change is expected to continue, follow these steps to prevent further automation errors.
Error message: Automation for the Project did not find any new dataset versions to run with
If your project failed to run due to this error, follow these steps to resolve the issue:
Error message: You do not have the required permissions: ExportDataSource, ImportDataSource
If you are receiving a message you do not have the required permissions, follow these steps to resolve the issue.