Why the Workflow Status Is Always "Running"?
In a migration workflow, the StartMigration and StartSynchronization steps take a long time, but other steps usually take less than 3 minutes. If your workflow has stalled for a long time, one possible cause is that the step execution results reported by Edge to MgC were lost.
Solutions
- Solution 1: Click the workflow name. On the Servers tab page of the workflow details page, you can view the status of the workflow on each source server.
- Solution 2: Contact technical support to check whether the tasks have been properly submitted and received.
Migration Workflows FAQs
- Why the Workflow Status Is Always "Running"?
- How Do I View the Migration Progress When the Migration Workflow Is in the Running State?
- How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
- How Do I Fix the Error "server require to bind credential first..." When the Migration Workflow Fails on a Source Server?
- How Do I Handle Resource Exceptions during a Batch Server Migration?
- What Are the Known Errors Related to Server Migration Workflows and How Can I Fix Them?
- What Can I Do If an Error Occurs During the Migration of a VMware Server?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore