Salesforce

In WorldServer, projects do not appear in the "Projects assigned to me" View and users assigned to a step are not getting notified

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer 11.1.1 and later version
Symptoms/Context
Although a Project or a Task is assigned to a User or Workflow Role, the assigned user(s) do not see that project in the Projects assigned to me view and in the WorldServer Home page stating if there are projects assigned to you.

User-added image

User-added image

Moreover, when going to Assignments > Background Jobs, you will find a long list of Update assigned and claimed tasks Jobs. You might see a long list of such job In Queue, but the first one executing as displayed here:

User-added image


 or you might see all the jobs in Queue and not executing:

User-added image
 
Resolution
1- If the assignments are being executed, you will have to wait until the assignments are completed. Once done, you will be able to see your projects under Projects assigned to me

2-  If the assignments are not being run and remain On Queue, restart the Idiom service. The STATS and the Background Engines will be restarted automatically. After the restart, you should see Jobs being executed. If a restart does not fix the issue, rebuilding indexes on certain Database tabled should fix the issue. Contact RWS Support creating a Support case for more instructions.
Root Cause
Starting from WorldServer 11.1.1., the projects and tasks assignments are run by an engine called STATS engine and are visible in the Background Jobs page as Update assigned and claimed tasks. These assignment jobs usually run very fast, 1 second each or lower. However, sometimes they might take longer or the number of assignments might be so high that a queue with these jobs is built.

Note: you need to refresh the Background Jobs often to make an assessment of what is going on. Assignment jobs are run very fast. Check the Job ID on the top, refresh and see if the same ID remains or if it disappears. If it disappears, the assignments are being processed, but the page View might not keep up with the change. If the JobID does not change and the status remains In queue, it means that the STATS engine - which is responsible for the assignments - is not running (root cause #2)

There can be 2 reasons for a delay in assignments:

1- The STATS Engine is running but there are a lot of jobs waiting because there are currently a lot of projects for many languages and with hundreds of files/tasks to be assigned
2- The STATS Engine is hanging and needs to be restarted
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by