Scheduling hope and best practices?

PointsWell

hpl123 wrote
hpl123 wrote
BobK wrote
Because of the issues with the logs, I do not use them much. But I believe that to get the rules executed via the scheduler to appear in the logs you need to select "Level of logging" of either "All server events excluding SQL" or "All server events including SQL"

I tested this last night and think I had full logs activated and the scheduled events did not get entries in the logs. Trying tonight again with full logs just to make sure.

Look like it does show scheduler events when you have full logs with SQL etc. enabled.

Seems like there should be a more obvious way to switch on login for scheduled processes, or rather the switch label should be more obvious. I have a process that I am trying to debug that generates a lot of erroneous records and debugging is a PITA.

gernotlg

BobK wrote
2) If a process crashes because of an internal error, the Switch for that process never gets set back to No, so this process would never run again. For this situation, I have another process that runs about every 15 minutes and checks each ControlRecord. If the ControlRecord Switch is Yes and the ControlRecord TimeStarted is more than 30 minutes ago, the Switch is reset to No. Under normal processing, my processes should not take 30 minutes to complete.

Is there a way to find out if a process is running programmatically. ?

I know that if we log in as admin we see the currently running processes in the system, and then cancel that process if we want, but in order to automate the cancelling of a Hung process, it would be good to be able to access the Active Processes query programmatically and then programmatically Cancel a process.

I'm just saying, because even if you check ControlRecord every 15 minutes (or whenever), and then mark a process as Switch = 'No', that process might still be running.... but just stuck.

kklosson

I had several scheduled processes that stopped working after a platform update. Turns out some were stating the time as 1400 and some were stating the time as 14:00. Those without the colon were broken.

hpl123

gernotlg wrote
BobK wrote
2) If a process crashes because of an internal error, the Switch for that process never gets set back to No, so this process would never run again. For this situation, I have another process that runs about every 15 minutes and checks each ControlRecord. If the ControlRecord Switch is Yes and the ControlRecord TimeStarted is more than 30 minutes ago, the Switch is reset to No. Under normal processing, my processes should not take 30 minutes to complete.

Is there a way to find out if a process is running programmatically. ?

I know that if we log in as admin we see the currently running processes in the system, and then cancel that process if we want, but in order to automate the cancelling of a Hung process, it would be good to be able to access the Active Processes query programmatically and then programmatically Cancel a process.

I'm just saying, because even if you check ControlRecord every 15 minutes (or whenever), and then mark a process as Switch = 'No', that process might still be running.... but just stuck.

Well, not a pretty one. If you know a little bit about databases, SQL etc. you can write some script or similar to dig through the execution_context table and empty the table to clear out all active processes. You can probably also figure out how to find and cancel/delete 1 particular row in the table for a particular process etc..

« Previous Page