The sites_by_species function in ALA4R expects the task status in PointsToGrid to return a status value of <=1 while it is busy off in the background.
(status values: 0 = in_queue, 1 = running, 2 = cancelled, 3 = error, 4 = finished )
In recent days the status query on the task takes a while to return a http 200 with the status value in it (eg 0,1,2,3,4).
Instead it returns http 500 for a while until it comes back with a "finished" status. But that's not technically correct, because it is actually processing the job. ALA4R should be able to expect to error if it gets a 500.
A 5 second delay before checking the status doesn't help.
@adam-collins @djtfmartin is there a spatial services issue that this can be linked to or should I create one?
The sites_by_species function in ALA4R expects the task status in PointsToGrid to return a status value of <=1 while it is busy off in the background. (status values: 0 = in_queue, 1 = running, 2 = cancelled, 3 = error, 4 = finished )
In recent days the status query on the task takes a while to return a http 200 with the status value in it (eg 0,1,2,3,4).
Instead it returns http 500 for a while until it comes back with a "finished" status. But that's not technically correct, because it is actually processing the job. ALA4R should be able to expect to error if it gets a 500.
A 5 second delay before checking the status doesn't help.
@adam-collins @djtfmartin is there a spatial services issue that this can be linked to or should I create one?