Learn about possible transformation errors that might occur when converting a process descriptor file, such as xPDD or BPMN. These errors are recorded in a text file found in the same folder as the process descriptor file.

There are six different types of errors that can occur during transformation. Some error types have additional details about the error encountered during transformation. Each error type is described below.

ControlRoomInteractionError
This error indicates problems while communicating with the Control Room APIs, either when retrieving the process descriptor file or when placing the transformed automation code files into the local repository. The error can be categorized into four specific API interaction failures:
  • User details API error: Failure when authenticating or retrieving user permission information.
  • Get file API error: Unable to download or access the required process descriptor file.
  • File list API error: Failed to retrieve the listing of available files from the repository.
  • Put file API error: Unable to upload or store the transformed automation code files.
InvalidUserRequestError
This error indicates an issue with the Autopilot service, that can occur from these possible causes:
  • Incorrect API parameters: The request contains incorrectly formatted or unsupported parameters that the Autopilot service cannot process.
  • Version incompatibility: A mismatch exists between the Autopilot service version and the Control Room version, preventing proper communication.
  • Back-end integration failure: The Autopilot service cannot properly connect with or exchange data with required back-end systems or dependencies.

These issues typically require administrative intervention to resolve the underlying configuration or compatibility problems.

OpenaiApiRequestError
This error indicates a communication failure between the Autopilot service and its back-end large language model (LLM). The issue is likely related to administrative configuration settings rather than end-user actions. Contact your system administrator to verify API credentials, service endpoints, and back-end availability.
InvalidLLMResponseError
This error indicates that while the Autopilot service successfully established connection with the back-end LLM service, it encountered an issue with the LLM's response. The communication channel is functional, but the response data is invalid, incomplete, or malformed.

Error: Failed to process LLM service response.

BadBPMNError
This error indicates an issue with either the structure of the input BPMN file or the Automation Anywhere process file generated by the service. This issue can arise from one of the following reasons:
  • Parsing error due to malformed or non-standard elements in the source BPMN file.
  • Unsupported BPMN constructs that cannot be properly translated.
  • BPMN structure that results in an invalid process file in the Control Room.
Errors:
  • Transformation created an invalid process structure.
  • Unexpected error creating process from BPMN.
BadxPDDError
This error indicates an issue with either the structure of the input Process Discovery process description document bundle (xPDD) file or the structure of the Automation Anywhere process file generated by the service. This issue can arise from one of the following reasons:
  • Parsing error due to malformed elements within the xPDD structure.
  • Corrupted or incomplete xPDD bundle files.
  • xPDD structure that results in an invalid process file in the Control Room.
Errors:
  • Error reading xPDD manifest.
  • Unexpected error creating process from xPDD.