Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For more information, see Run Job Page.

Tip

Tip: Information on failed plan executions is contained in the orchestration-service.log file, which can be acquired in the support bundle. For more information, see Support Bundle Contents.


Identify Job Failures

When a job fails to execute, a failure message appears in following locations:

...

In the above example, the Transform and Profile jobs completed, but the Publish job failed. In this case, the results exist and, if the source of the problem is diagnosed, they can be published separately.From the job's context menu, select Download Logs. You can download the jobs logs to look for reasons for the failure. See Review Logs below.

Invalid file paths

When your job uses files as inputs or outputs, you may receive invalid file path errors. Depending on the backend datastore, these can be one of the following:

  • Path to the file is invalid for the current user. Path may be been created by another user that had access to the location. 
  • Path contains invalid characters in it. For more information, see Supported File Formats.
  • Resource was deleted.

Jobs that Hang

In some cases, a job may stay in a pending state indefinitely. Typically, these errors are related to a failure of the job tracking service. You can try to the following:

...