How to stop jobs getting faulted

[mohamedalthaf]

Hi,

The below is my trigger setups.

VM1-Queue Trigger-Runs on item availaility
VM2-Time Trigger-9:15 AM & 3:15 PM Stop time: 10:00 PM

1.Both run the same process
2.Each trigger is linked to a different environment/robot (VM)

The issue here is, At 3:15 PM, the second (time) trigger fires on VM2, but a previous job (from 9:15 AM) is still running. I created the second time trigger (3:15 PM) as backup. Incase 9.15 AM jobs fails, as backup at 3:15 PM will work which I thought will be helpful in processing more items in the queue.but my 9.15 AM got stopped and marked as faulted eventhough I didn’t send any stop signal around 5PM. Also the same process running in VM 1 based on queue trigger also got stopped and marked as faulted around the same time 5PM. is this due to second time trigger I set at VM2 and it’s failure to run process at 3.15 PM. I checked chatgpt it says the issue is due to second time trigger. But if the issue is with time trigger it should stop process execution at VM 2 only right. Why VM 1 process also got stopped

Can anyone clarify

[arjun.shiroya]

Hi, @mohamedalthaf

Create separate process packages for each trigger e.g-Process_VM1 and Process_VM2 instead of using one process in two triggers.

[Anil_G (Anil Gorthi)]

@mohamedalthaf

Please check event viewer logs on the machine around the failed timestamp

I dont think triggers would have effected

cheers

[prashant1603765 (Prashant Kumar)]

Hi @mohamedalthaf

both triggers run the same process in the same folder, so when the 3:15 pm trigger started it caused a conflict in orchestrator, stopping the running jobs. keep them in separate folders or avoid overlap.

Happy Automation