Hi all,
The last couple of days I have been getting inundated with errors and warnings from multiple scenarios we use with Field Maps mobile and Integromat. I can temporarily fix the issue by going in and re-validating the connection but it doesn't hold very long until I get more errors. Are there any current issues with Field Maps?
@tbearb , just to keep this going, I'm still having the issue and have done everything in my power to initiate a fix. Here's the last response I got from Make on March 30th:
Interesting, we have a support case open with them regarding the migration from Integromat to Make and this was one of the issues we have sent them. They have been pretty slow to respond unfortunately.
Thanks for the response! I reached out to Make as well to see if they could give an update, and I got this response:
They replied this morning that their Apps Development team is looking into it.
We are also getting the same error. I can fix it for a couple reports, but then it starts right back up again with Code 498.
I'm going to contact our Esri Rep - see if I can get ahold of someone at Survey123, contact Make, and also work with our GIS Admin to see if there is some kind of workaround in the meantime.
Any resolution for this yet?
@AdelaideZumwalt1 were you able to get anywhere after you made your contacts to Esri / Make? Or has anyone here had recent success on obtaining an update on this issue? I'm tired of getting bounced around from Esri support to Make support and having to constantly revalidate the token every day.
@tbearb I heard back from Make Dev/Customer support on May 31st.
just to keep you posted. Our development team is still working on the issue. We were able to reproduce the error in production development while in staging not.
I will inform you once we have more info.
I was not - but I haven't followed up either. Thank you Aaron Pulver for the update. We would really like to move to Make as soon as possible, right now Make reverted our models back to Integromat... so we are back to Integromat.
This issue should be resolved now. Our support ticket with Make was updated this morning. Preliminary testing appears promising.
Thanks for the update @Anonymous User !