-
Title
Dirsync workflow read taking longer than normal to complete -
Description
Running Dirsync workflow for three hours now which is 50% longer than it has taken in recent history - can someone please check to ensure it is legitimately taking this long and not hung? Why is this so slow? -
Cause
Product feature enhancement Deployment.
Possible Azure issues in specific region. -
Resolution
Tuesdays and Thursday are product enhancement and maintenance deployment days. This can affect the speed and throughput of product tasks like Discovery and Workflow tasks. A workflow which normally takes 15 minutes, can take 45 minutes to complete.
To confirm the workflow is not hung, open the current workflow log, and look at the last row number and time stamp to see when the last update was recorded.
Then check the log again in 5 or 10 minutes. There should be additional entries since you last checked.Allow the task to complete, and do not stop it.
Contact Product Support if it's not Tuesday or Thursday and the task has not progressed in the last hour.
Provide the following information to Support:
Product Client Name (Org Id if ODM Dirsync)
Dirsync Log
Workflow Name or Environment name if running a Discovery
Discovery Log
-
Additional Information
The issue may also be caused by Azure outage in the specific region.