Latest Contributions by TylerBragg2

‎06-15-2021

This is interesting, because I'm primarily experiencing this with the webform, though I have experienced it with the mobile app as well. We have one survey where users (public) apply for new utility service with our municipal sewer department (through the Survey123 webform), and that's the primary one that seems to experience this problem. So given that this is coming from the webform and not the mobile app, what could be the cause of that? And does this new update do anything to fix it?

‎06-14-2021

That's not a bad idea at all. But, I'm thinking we could rule out connectivity issues as the cause because the webhook is not initiated at the mobile level; rather, it should be issued by ArcGIS Online at the feature service level(at least in my case, unless you are using Server, then from there). That's where a log file from AGOL would be nice so you can compare the submit time/date of the feature and the log file of webhooks to see if it skipped one. I'm thinking that's what's happening. But what you mention would be a good way to validate that. Or, I suppose there could be a blip with Integromat where it was NOT listening for a certain time period. Then AGOL could have sent the webhook but Integromat never saw it because it wasn't listening. In that scenario, Integromat wouldn't show it in the scenario history because it truly didn't receive it, even if it was because it "wasn't listening."

‎06-14-2021

I've been having this happen to me as well, and it seems to be more often in the last few months. I have a paid subscription to Integromat and have 28 active scenarios running at all times, some of them being somewhat complex, some being fairly simple. I actually had this happen last week and again today on a scenario that has been running for about a year now with very few problems. The user reported the problem to me but I can't seem to nail down the source, except that it must be in the webhook. I checked the history of the scenario in Integromat and there are no errors, and more importantly, no record of the trigger at all. I've tried to look on the Survey123 side and I can't seem to find a way to validate that the webhook trigger was sent to Integromat. Then the next submission of the survey will work perfectly.

‎06-14-2021

I agree with this. I've had several issues with Survey123 not sending webhook triggers to Integromat, and I've been trying to find a way to check a log. I'm guessing there isn't one. If not, there should be a way to check that. I'm sure it's logged somewhere.

‎05-17-2021

@DanteLee - I still have an open case with ESRI Tech Support and we have not come to a conclusion yet. I'll post when we come up with something.

‎04-27-2021

I grabbed some screenshots of the errors: Below is the error I get when launching the survey from the web map popup that I use in Field Maps. This is described in item # 2 above. This was actually generated on the desktop from Map Viewer Classic, but I get the same error when launching it from Field Maps. If I simply launch the Survey123 web app from my AGOL home page, shown here: Then close the survey123 web app, I can successfully launch the survey from the web map popup and access the survey with no problems, shown here: Notice the Icon and my name in the upper right of the screenshot above. After I've launched the Survey123 web app from the browser it recognizes me as being logged in and allows me to access the survey. I generated these errors from the desktop, but again, I'm getting the same problem from a mobile device.

‎04-27-2021

I have been experiencing a problem with Survey123 not recognizing users as being logged-in in several scenarios. These surveys have been established and working for more than a year, and this problem has come up in the last few months. There are two scenarios so far, and they are as follows: I have a several surveys embedded in different dashboards, all of which are configured to open in edit mode within the dashboard. One example is a Yard Sale Permit. The survey itself is open to the public, and the public uses this survey to submit an application for a Yard Sale Permit. The dashboard is for our staff to view the permit information and makes necessary modifications. In order for the staff to view the dashboard, they must log in to AGOL, then open the dashboard. The problem is that the embedded survey does not recognize them as being logged in and generates an error that will not allow them to submit edits. (When a user is logged in, their user name and picture icon is present in the top-right of the survey window, but this is not showing up). However, if the user opens the survey123 web app from our org's AGOL home page first, the embedded survey loads just fine and will allow them to make edits and submit with no problems. This was not a problem until just a few months ago. We are using Windows 10 with the Google Chrome browser. I haven't tested with other browsers at this time. I have a map for use in the Field Maps mobile app, and I've configured the pop-up to contain a link to a survey that opens in the web form in edit mode. Again, this was working fine with no problems until a few months ago, and now when the user (who is logged into the Field Maps app) launches the survey from the pop-up, they receive an error that they don't have permissions to access the survey. Again, when this happens, there is no username or picture icon in the upper right of their survey. However, if you open the browser and go to our org AGOL home page, log in, then launch the survey123 web app, then go back to Field Maps and launch the survey, it functions properly and the survey shows them as being logged in. I have tested this with Chrome and Samsung Internet and experience the same issue. It appears that there is some problem with the user's credentials getting passed to the Survey123 web form in both desktop and mobile environments, and with different browsers. I've searched the community forum, and have yet to find anyone with this same issue. I did find a thread that talks about a similar problem and suggests making changes to the Chrome settings for "Same site cookies" and "Preloading pages for faster browsing," but I've tried changing both of those settings to no avail. Here's the thread: Embedded Survey123 Web Form works for some but not others . There were two suggestions in this thread, neither of which seem to solve the problem for us. I hope I've explained this problem well enough, but I'd be happy to answer any questions that may help to find a solution. I can also provide some screen shots if needed - I just didn't have them at the time of writing this question. Thanks. Tyler Bragg

‎04-26-2021

Charlie, I'm having a similar problem, described in my recent thread here. Not exactly the same, but I have a case with technical support open as we speak. Ultimately, we think my problem may have something to do with the say Survey123 is understanding the URL parameter for the GlobalId. I'm getting a "Failed to Submit" problem using the syntax you described above. We still aren't sure what's going on, but we will get to the bottom of it. I don't know what changed, but my issue seemed to start immediately after the April 13th update of AGOL. When did your start giving you problems?

‎04-21-2021

Will do Craig. Thanks again.

‎04-21-2021

@CraigGillgrass ok, thanks. I'll do that. If we come to a resolution, I'll make it a point to report back here for closure on this issue.

‎04-21-2021

@CraigGillgrass How exactly would I capture that HAR, since I'm interacting with my mobile to AGOL and it's not running through my desktop?

‎04-21-2021

@CraigGillgrass what do you mean by "...check that all the required fields for Workforce Assignments layer are filled in and entered..."? I specifically omit all the required Workforce fields from my survey so as to prevent duplication or possible data overwrite situation with Survey123 submission vs. Workforce sync. I only use the Survey to fill out the additional attribute fields that I've added to the Assignments layer. The main Workforce fields are filled out in the Workforce App, then the "Survey at Assignment" is launched and the survey is filled out and submitted, which populates the attribute fields that are not available in Workforce. Should I be doing this differently? I don't understand why this was working prior to the AGOL update and now it's not. Here's my URL that's set up in the Assignment Integrations layer: https://survey123.arcgis.com/share/<itemID>?mode=edit&globalId=${assignment.globalid}&version=latest Can you see anything wrong with this? This should be the correct syntax, as it was working initially (Prior to April 13). Craig, we discussed this in another thread recently (here). Also, as a troubleshooting measure, I created a brand new survey in Survey123 Connect yesterday afternoon based off the Assignments feature layer. I wanted to eliminate any problems with the configuration of my xlsform that I've been working with. I made no configuration changes to this "stock" survey build directly from the feature layer, other than removing the workforce-specific fields, then published and changed the Assignments Integration link to the new survey. It still produces a "Failed to Submit" error. So it doesn't appear that the problem is in the xlsform configuration. For some reason it seems as though this project has been plagued with problems...more so that usual. Thanks for everyone's help.

‎04-20-2021

Yeah, I can't quite figure what's going on. Especially since it was working prior to the April 13 update. Maybe @CraigGillgrass would have some insight? Or maybe @JamesTedrick. This seems to be a cross between a Workforce and Survey123 issue, but I'm thinking it's leaning towards Survey123. Actually, it could be something I've done that I'm just not seeing. I just don't know at this point. I've been banging my head against the wall on this since last week, and I seem to be stuck. Tyler

‎04-20-2021

Here's another weird twist to the story: When I launch the survey from Workforce, the survey opens properly, I fill out all the information, then click the submit button. I then get "Failed to Submit." So I close out the web browser that contained the survey, which brings me back to Workforce. If I immediately launch the survey AGAIN, it opens the survey will all my answers filled in. If I scroll down and click the submit button, the submission goes through successfully. Also, I just downloaded Survey123 Connect 3.12 and re-published the survey, just to eliminate that as the issue. I still get the same behavior I've described above. Tyler

‎04-20-2021

Josh, Thanks for the reply. I've checked the sharing settings and I can't seem to find any issues. I've had problems with that on other surveys, but for right now it is only me attempting to submit the survey, and I'm the org admin and the owner of all the data. Here are my sharing settings for the survey: I don't think the alias has changed. It's still listed as "Assignments."

Online Status	Offline
Date Last Visited	‎11-12-2025 12:18 PM

My Ideas

Latest Contributions by TylerBragg2

Re: Webhooks not triggering randomly

Re: Webhooks not triggering randomly

Re: Webhooks not triggering randomly

Re: Provide Webhook Logging

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Survey123 web form not recognizing logged-in user when opened from Field Maps or Dashboard in Chrome (desktop and mobile) and Samsung Internet

Survey123 web form not recognizing logged-in user when opened from Field Maps or Dashboard in Chrome (desktop and mobile) and Samsung Internet

Re: Editing is not possible because the record specified by the globalId parameter cannot be accessed

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Survey123 web form not recognizing logged-in user ...

Re: March 2022 update of Dashboards malfunction wi...

March 2022 update of Dashboards malfunction with e...

Strange behavior with photo uploads in existing su...

Re: Webhooks not triggering randomly