topic Re: Field Maps module in Make (formerly Integromat) in ArcGIS Field Maps Questions

Field Maps module in Make (formerly Integromat)

DEI — Thu, 02 Mar 2023 16:37:14 GMT

Hello,

Make (formerly Integromat) scenario with ArcGIS Field Maps module was working fine yesterday, today I keep getting "The operation failed with an error. Body is not a valid JSON. Unexpected token in JSON at position 0". Haven't made any changes to the scenario since it was set up. I tried reauthorizing the connection but that didn't help. Anyone have similar issues? Any thoughts on how to resolve while retaining queued data?

Re: Field Maps module in Make (formerly Integromat)

JustinColville — Thu, 02 Mar 2023 17:32:36 GMT

Hello,

In Make, under the Webhooks section you can look at the Logs tab and see details about each time the hook was triggered (similar to the images below). What does the Body of the requests that are failing look like?

Regards,

Justin

Re: Field Maps module in Make (formerly Integromat)

DEI — Thu, 02 Mar 2023 18:46:23 GMT

Thanks @JustinColville ,

The logs under the Webhook section display 'Success' under Status.

but in the Scenario, it shows the error.

Re: Field Maps module in Make (formerly Integromat)

DEI — Thu, 02 Mar 2023 19:10:32 GMT

Something I noticed - I have 2 connections running similar scenarios. One connection is ...services3.arcgis.com (this is the one related to the issue) and the second is ...services6.arcgis.com which is running fine as of now (knock on wood).

Re: Field Maps module in Make (formerly Integromat)

JustinColville — Thu, 02 Mar 2023 20:03:37 GMT

Thank-you for sending the additional info.

If you setup a new webhook for the same service does it work correctly?

Are you able to run an extractChanges REST API call in a browser similar to changeURL in the Body of the 9:52am webhook? Does that complete successfully and return valid JSON?

Re: Field Maps module in Make (formerly Integromat)

DEI — Thu, 02 Mar 2023 21:23:43 GMT

At some point within the last hour or so everything automagically started running again. Bizarre but appears all good now. However, I have no explanation for the behavior.

Thanks for your time @JustinColville !