After deploying a new snapshot to your BPM 7.5.1 Process Server environment, are you noticing that your Undercover Agent (UCA) is not firing on your set schedule? I noticed this after deploying an application that uses a scheduler event and it should fire at certain times that were decided upon by the development team. I first noticed this be checking in the BPM Process Admin console:
Here, the Event Manager Monitor shows you the scheduled events. If you notice that the schedule is not correct, as per what the developer set in the application in Process Designer, you can actually change these value in the BPM database (BPMDB). There is a table called LWS_EM_TASK, where you can edit the scheduled times and the repeating schedule:
After you commit the changes to the database, you can then log back into BPM Process Admin and view the changes you made in the Event Manager Monitor. The UCA should then kick off at the next scheduled time that you scheduled for.