Troubleshooting and FAQ

this section describes common migration issues and the recommended resolution steps global catalog item not found some global catalog items available in aiops automation services (as) are intentionally not migrated to bridge automation service (bas) if a global catalog item is not available after migration review the global approved catalog items for migration section verify whether the catalog item is included in the approved migration list confirm that the migration completed successfully if the catalog item is included in the approved list but is still unavailable, contact the migration support team only catalog items approved for migration are made available in bas catalog items that are not included in the approved migration list are not migrated tenant catalogs, workflows, schedules, or events not found if private catalogs, workflows, schedules, or events are not available after running the aiops automation services migration catalog item, review the migration workflow execution to identify failed migration activities review migration failures from the main menu , go to services → platform services → bridge automation → workflow executions locate the aiops automation services migration workflow execution select the more actions menu ( ) and then select view details open the activities tab review the activity list and identify activities with a failed status open the failed activity and review the error message determine the cause of the failure resolve the reported issue, such as missing prerequisites configuration issues permission related issues credential related issues run the migration catalog item again verify that the previously missing catalogs, workflows, schedules, or events are available in bas review migration summary a high level summary of migration results is available in the summarize migration activity within the workflow execution the summary provides information about successfully migrated items skipped items failed items migration statistics for additional details, review the output parameters tab of the migration workflow execution retry a failed workflow execution if a workflow execution fails, the workflow can be restarted after the underlying issue is resolved restarting a workflow executes the automation from the beginning before restarting the workflow, confirm with the delivery platform engineer (dpe) that the automation is safe to rerun and supports retry operations restart a workflow perform the following steps to restart the workflow from the main menu , go to services → platform services → bridge automation → workflow executions locate the workflow execution with a failed status select the workflow execution to view its details select the more actions menu ( ) select restart workflow review the workflow inputs confirm the restart request monitor the execution from the workflow executions page until it is completed