What Can I Do If Flow Control Is Triggered During Migration?

If a large number of migration tasks fail and error 503 is recorded in the failure object list, the flow control may be triggered. You can handle the issue as follows:

1. Check whether flow control is triggered at the source.
   • If it is, contact technical support of the source platform or submit a service ticket to increase the flow control limit.
   • If it is not, contact technical support of the target platform or submit a service ticket to increase the flow control limit.

2. (Optional) Adjust the maximum number of concurrent subtasks in the migration workflow. Reducing the maximum number of concurrent subtasks may decrease the migration speed.
   1. Click the workflow name to view its details.
   2. Click the corresponding resource name. View the Migration Progress area.
   3. Click Modify above Expected Concurrent Subtasks and configure an appropriate value. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, the maximum number of subtasks can be 20 or any number below.

      

   4. Click Confirm.

3. Retry the migration workflow.