Force stop a long running Map automatically
Hello,
Is there a way to force stop a scheduled Map job that has been running longer than usual? We have one MAP that runs once every 24 hours. The job itself should only take about 1 hour. If it’s longer than this, then that means something went wrong. Then the next day it won’t run again because the job is “locked” by the “system” account. So we don’t get any notification that it’s not running. I have to open the Map and clear the lock so I can open the Map and manually run it. It usually runs fine the next day too. Just once in a blue moon, it gets stuck. If we don’t check to see that it’s stuck… it stays like that for days until an end user sees missing/wrong data.
So…I’d like to know if we can put a 2 hour timeout on a job that will force clear the lock. So that It can run again the next day.
Is there a way to force stop a scheduled Map job that has been running longer than usual? We have one MAP that runs once every 24 hours. The job itself should only take about 1 hour. If it’s longer than this, then that means something went wrong. Then the next day it won’t run again because the job is “locked” by the “system” account. So we don’t get any notification that it’s not running. I have to open the Map and clear the lock so I can open the Map and manually run it. It usually runs fine the next day too. Just once in a blue moon, it gets stuck. If we don’t check to see that it’s stuck… it stays like that for days until an end user sees missing/wrong data.
So…I’d like to know if we can put a 2 hour timeout on a job that will force clear the lock. So that It can run again the next day.
Answers