Handling orphaned transactions in the Transaction Manager when creating a new M3 issue

Failed Create Issue Header or Create Issue Line transaction may result in orphaned transactions in Transaction Manager. Orphaned transactions are left in Unsubmitted Transactions list with For Resending status and database transaction exception.

Using the Transaction Manager, navigate to Processed Transactions.
Search for transactions with error logs or exceptions.
Select the corresponding failed transaction from Processed Transactions list.
Click Cancel or Delete to remove the dependency which causes the orphaned transaction.
Click the ellipsis button and proceed to Unsubmitted Transactions.
Identify which orphaned transactions have For Resending status and a database transaction exception.
Click the ellipsis button and then click Resend transactions to submit the transactions to M3 Mobility Core.

Notice that M3 Mobility Core now successfully processes transactions because the dependency on the failed transaction no longer exists.
After resending the orphaned transactions, navigate to Processed Transactions.
Verify that the orphaned transactions are successfully processed without any further errors or exceptions.

Ensure to review failed transactions and to resolve it promptly to avoid longer delays in issue processing. If the Resend action fails, check for specific error messages or exceptions.