221 lines (142 loc) · 4.38 KB

Statuses of Transport Requests

A transport request can have an import status in an import queue and a lifecycle status in the transport requests overview.

Import statuses of transport requests in import queues:

Import Status in Import Queue	Description
Deleted	The transport request was removed from the import queue of the transport node. For more information, see Remove Transport Requests.
Error	The import of the transport request took place, but errors occurred for one or more objects. This means that the content of the transport request was only partially imported or imported with errors. Since the content causes the error, re-importing it won't resolve the issue. You can only re-import transport requests with an Error status after you've manually reset them. Requests with an Error status aren't included in an Import All action.
Fatal	No objects from the transport request were imported. This can happen if the deployment process doesn't start due to issues like an incorrect destination or insufficient authentication. If the application issues a rollback during an import, this also results in a Fatal status. You can re-import transport requests with a Fatal status. They're also included in an Import All action.
Initial	The transport request was added to the transport node, but an import hasn't yet started.
Repeatable	The transport request was earlier in an Error, Skipped, or Succeeded status and was manually reset - with the aim of restarting the import.
Running	The import of the transport request is currently running.
Succeeded	The import of the transport request in the transport node was successful.
Skipped	The import of the transport request in the transport node was intentionally skipped. The Skipped status is equivalent to a Succeeded status. It can occur in the following situations: For all imports into virtual nodes, since physical imports into virtual nodes aren't possible. For imports of the content types BTP ABAP and application content in situations where the deploy target has skipped the content deployment of the transport request.
Transient	A modifiable transport request was previously tested in the transport node and then released. Releasing the request changes its status to Transient in the import queues of follow-on transport nodes. This ensures the traceability of these requests.
Warning	Warnings occurred during the import of the transport request in the transport node.

Lifecycle statuses of transport requests:

Lifecycle Status in Transport Requests Overview	Description
Archived	The transport request has a final status in all import queues and was set to Archived by the automatic cleanup run of SAP Cloud Transport Management. For more information, see Storage in SAP Cloud Transport Management: What To Know.
Deleted	In all import queues that the transport request was part of, it has the status Deleted.
Modifiable	The transport request is modifiable. For more information, see Processing Modifiable Transport Requests.
Released	In at least one import queue the import status of the transport request isn't Archived or Deleted.