I am not sure what is happening here but it looks like an event in my scheduler object (v10) is recreated every day and keeps the old event running. I have a simple database event that starts a workflow using ACTIVATE_UC_OBJECT and a scheduler that hosts this event (start time 15.45, turnaround 00:00 each day, 0 concurrent processes).
After running the scheduler for one week I somehow ended up with 5 active events. I don't think it is supposed to work that way; can anyone tell me what I am doing wrong?
My scheduler and the eventhttps://us.v-cdn.net/5019921/uploads/FileUpload/fa/b51a6ab9f6c43066a0d4eeb9cac2aa.png" width="675">
The execution/activation of the event
Statistics of the last week
I don't understand why I see 5 "sleeping" events which start time (according to their running time) is separated by 48 hours each. Also, I don't get why the activities window shows the event was executed every day at the start time and can't give me a status. I think I can fix the behavior by altering the number of concurrent processes to '1' but I want to understand why this happens... Any help is appreciated!
When you put an Event in a Schedule, it will be kicked off each day, but the previous one will stay running as well unless it's scripted to end at the end of the day or only one occurrence is allowed.
Thanks for your reply. I am not sure I understand what you mean by "fulfilled" events; the events check repeatedly every 5 minutes whether the number of records returned by a query is larger than 0.
This is actually a process running at our test server so nothing has happened the last week and the event did not occur at all. I updated a record to make the event occur and it was quite interesting to see the process running simultaneously for 5 time - which, of course, failed -.
Do I understand it right if I should change the number of concurrent processes to 1 for both the event and the workflow started? I figured one event should run eternally in a scheduler but apparently it consists of day to day runs...
Thanks for the additional info.
'Fulfilled' means that the parameters set for the event have been met.
Objects in a schedule are executed every day, so it makes sense why there were multiple Events running if the 'event' never happened. Changing the number of concurrent processes to 1 will be the best way to ensure only 1 Event is running at any given time.
We use the following for most continuously executing Events:
1. Use the Runtime MRT to Curr.date + 1 Day(s) and the Time to 7:55 (for example) for the Event.
2. Set the Event's Max. Number: to 1 Else Abort.
3. Place the Event on the Schedule for daily at 8:00 (for example) execution. In the above example the Event's Check in intervals of: 15 and First check Immediately.
You would adjust the Runtime and Schedule start to coincide with the Event's interval to ensure that it is executing as appropriate.