Problem with status update of asyncronous geoprocessing task at 3.1

Discussion created by sthorntonesri-ireland-ie-esridist Employee on Sep 13, 2012
Latest reply on Nov 4, 2013 by JGravois-esristaff
Hi All,

I'm having a problem updating from 2.8 API to 3.1.

I have a geoprocessing task working great at 2.8 and I can see the status of the task while it is running.

However when I use the 3.1 API the callbacks to check the status fail after the first status callback.

The error I see in Firebug is 'Job abc123 is does not exist or is inaccessible' (See attached for screenshot). However the job does exist and actually runs
to completion as my expected output file is generated correctly.

Has anybody else come across this issue? Any workarounds?

Any help would be greatly appreciated.