After I posted yesterday I created a new service which runs the following:
runner = 0
while runner < 30:
arcpy.AddMessage("Run {}".format(runner))
time.sleep(60)
runner += 1
And noticed the following behavior:
After approximately 10 minutes:
Job Details: j01d59f56600943ff8bb75d8cbc9445dd (Dummy)
Job ID: j01d59f56600943ff8bb75d8cbc9445dd
Job Status: esriJobFailed
Job Messages:
- esriJobMessageTypeInformative: Submitted.
- esriJobMessageTypeInformative: Executing...
- esriJobMessageTypeInformative: Executing (Dummy): DummyTool
- esriJobMessageTypeInformative: Start Time: Thu Nov 1 15:42:09 2018
- esriJobMessageTypeInformative: Running script DummyTool...
- esriJobMessageTypeInformative: Run 0
- esriJobMessageTypeInformative: Run 1
- esriJobMessageTypeInformative: Run 2
- esriJobMessageTypeInformative: Run 3
- esriJobMessageTypeInformative: Run 4
- esriJobMessageTypeInformative: Run 5
- esriJobMessageTypeInformative: Run 6
- esriJobMessageTypeInformative: Run 7
- esriJobMessageTypeInformative: Run 8
- esriJobMessageTypeInformative: Run 9
- esriJobMessageTypeInformative: Run 10
- esriJobMessageTypeError: Failed.
- esriJobMessageTypeInformative: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.
But after pressing refresh I could see that the job was continuing to the end of the script:
Job Details: j01d59f56600943ff8bb75d8cbc9445dd (Dummy)
Job ID: j01d59f56600943ff8bb75d8cbc9445dd
Job Status: esriJobFailed
Job Messages:
- esriJobMessageTypeInformative: Submitted.
- esriJobMessageTypeInformative: Executing...
- esriJobMessageTypeInformative: Executing (Dummy): DummyTool
- esriJobMessageTypeInformative: Start Time: Thu Nov 1 15:42:09 2018
- esriJobMessageTypeInformative: Running script DummyTool...
- esriJobMessageTypeInformative: Run 0
- esriJobMessageTypeInformative: Run 1
- esriJobMessageTypeInformative: Run 2
- esriJobMessageTypeInformative: Run 3
- esriJobMessageTypeInformative: Run 4
- esriJobMessageTypeInformative: Run 5
- esriJobMessageTypeInformative: Run 6
- esriJobMessageTypeInformative: Run 7
- esriJobMessageTypeInformative: Run 8
- esriJobMessageTypeInformative: Run 9
- esriJobMessageTypeInformative: Run 10
- esriJobMessageTypeError: Failed.
- esriJobMessageTypeInformative: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.
- esriJobMessageTypeInformative: Run 11
- esriJobMessageTypeInformative: Run 12
- esriJobMessageTypeInformative: Run 13
- esriJobMessageTypeInformative: Run 14
- esriJobMessageTypeInformative: Run 15
- esriJobMessageTypeInformative: Run 16
- esriJobMessageTypeInformative: Run 17
- esriJobMessageTypeInformative: Run 18
- esriJobMessageTypeInformative: Run 19
- esriJobMessageTypeInformative: Run 20
- esriJobMessageTypeInformative: Run 21
- esriJobMessageTypeInformative: Run 22
- esriJobMessageTypeInformative: Run 23
- esriJobMessageTypeInformative: Run 24
- esriJobMessageTypeInformative: Run 25
- esriJobMessageTypeInformative: Run 26
- esriJobMessageTypeInformative: Run 27
- esriJobMessageTypeInformative: Run 28
- esriJobMessageTypeInformative: Run 29
- esriJobMessageTypeInformative: Completed script DummyTool...
- esriJobMessageTypeInformative: Succeeded at Thu Nov 1 16:12:10 2018 (Elapsed Time: 30 minutes 0 seconds)
Job Status says failed but the last message says succeeded. I think it's a bug and will report this to Esri.
By the way, when I set the timeout to less than 10 minutes, the job is terminated after the time period.
Robert