Showing results for 
Search instead for 
Did you mean: 

We're looking into an issue with broken attachments right now. Please stay tuned!

Handling Common Paxata Automation Errors

Linear Actuator

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.



Common Error Situations with Automation

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:

  • Library import failed



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:

  • New datafile versions found, but the columns are different

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:

  • Automation for the Project did not find any new dataset versions to run with

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:

  • You do not have the required permissions: ExportDataSource, ImportDataSource

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.





Recovering from Errors in Automation

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



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.

  1. Go to the library and find the automated dataset.
  2. Click on the properties icon to the right of the dataset
  3. Click on the "Projects" link on the left and note which projects reference this dataset
  4. Open each project noted in step 3 and do the following
    1. Select the step in the project where the dataset is referenced
    2. In Edit mode, click the dataset button at the top of the screen
    3. Select the data set you wish to use (the latest version of the existing data set)
    4. Save the Project
    5. At the top of the Project screen, click the blue, Automation Outdated refresh button

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:

  1. On the Automation page, under Job Details, note all the Import Datasets listed in the failed job.
  2. Determine if any of the Import Datasets failed to update. If so, resolve the library update issue and re run the project. If not, continue to step 3.
  3. On the Automation page,
    1. review the Active Schedules for the project and all associated datasets. Ensure that the datasets are scheduled to run before the project. Pay particular attention to details such as AM/PM.
    2. Review the Job Details for all datasets associated with the project. Look at how long it took to run each dataset update. Do the datasets have sufficient time to finish updating before the project automation starts?
  4. Confirm all associated datasets are truly associated with a project by reviewing the Project Automation page and comparing the Import Datasets schedule time and the project Schedules times.
  5. If you are still not able to identify the cause, take note of the last successful run of the project automation and the last successful run of all associated datasets and send this information to Paxata Support

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.

  1. Ensure you, the user who has scheduled the job, has the necessary rights export to that specific data source by manually exporting a dataset to that data source.
  2. Open the project
  3. Click on Automation button (top tool bar)
  4. In the Publish AnswerSets section, review each publish lens and the data source configuration.
  5. Save the Project Automation Job once there are no errors on the form
Labels (1)
0 Kudos
0 Replies