Description
There are 200-220 pending items in Winshuttle update background jobs and it's taking 2 to 3 hours for any of them to be processed.
Applies To
11x;12x
Solution/Immediate Workaround
Steps to be performed to troubleshoot the issue.
Background Job taking long-time to run the Winshuttle Update Plugin
Comments
0 comments
Please sign in to leave a comment.
2. Check the workflow and verify how many update plugin or any other plugin are present in single step.
3. Check all update plugin are configured in sync mode
4. Check what is the key value for "WinshuttleWebServiceRunAsync" in Configuration Options.
5. Check on Sever SVService job for WINSHUTTLE update plugin whether it is running and also whether this job is configured for some other job type and also check the frequency of the job.
1. Create a dedicated job for WINSHUTTLE update plugin .Depending how many plugins are used in solution if there are more than 2 plugins used in single step and solution is complex ; it is recommended to configure two separate jobs , 1 for Winshuttle Update Plugin and Another one for Winshuttle update async with 1 min in frequency. See attached link how to create the jobs.
4) Make sure key “WinshuttleWebServiceRunAsync” is set to “true” from workflow Configure Options page. See below link how to do so.
Key Configuration
5) If you have more than one WFE's make sure to perform the above mentioned steps on all the WFE's.