topic Generate status doesn't always result in an error even when it has errored in ArcGIS AppStudio Questions

Generate status doesn't always result in an error even when it has errored

Anonymous User — Mon, 18 Jul 2016 03:14:08 GMT

This question possibly has wider considerations, but in my particular case it relates to generating and syncing geodatabases.

When I generate or synchronize a geodatabase with a feature service, occasionally something might go wrong and the request will fail. But an error code is not always raised.

For example, I called geodatabaseSyncTask.generateGeodatabase, and I could see the 'GenerateStatus' change to 1 (which means InProgress), but then it never changed from that. When I checked Fiddler logs, I saw a 400 response saying "description=Failed to parse geometry from input JSON". The Fiddler log error makes sense and I have no issue with that, but I would have expected the sync task generate status to change to 3 (error).

But I do notice that the usual continuous polling for an update on the status of the job stops, so the sync task must somehow be aware that the job has an error??

So , my question is twofold - is this a bug, in that it should be returning this as an error? And, is there any other way to catch these reponses?

A similar thing happens when synchronizing, only certain errors actually create an error, meaning that from the application perspective there is no way to tell if the sync process is still under way.

Re: Generate status doesn't always result in an error even when it has errored

nakulmanocha — Mon, 18 Jul 2016 20:31:07 GMT

Hi Paul,

We need to test this scenario. Could you please log a ticket with the Technical support?

Thank you.

Nakul

Re: Generate status doesn't always result in an error even when it has errored

JohnPlunkett — Mon, 18 Jul 2016 22:22:16 GMT

I have logged a call

Esri Case Number 01805501 -

Re: Generate status doesn't always result in an error even when it has errored

nakulmanocha — Thu, 28 Jul 2016 00:18:29 GMT

Hi Paul,

I haven't been able to reproduce the issue. I tried the invalid extent approach to throw an error to simulate the workflow. But it does get reflected in the generatestatus code. I mean changes from 1 to 3. Where 3 implies error.

-Nakul