nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey123 Create Report in Power Automate Error

RalphPlummer

Hello

I'm in search of suggestions or ideas one why this problem keeps happening. I thought I had the workaround for it, but apparently it is not. Here is the error I keep seeing when the create report is triggered. It is random and has no rhyme or reason.

Create report will show:

The problem isn't the upload file from URL, it is the create report step. It doesn't generate the report due to the missing token and causes the Upload file from URL to fail since there is no file to upload. When I pull up the raw output, this is what it says:

{

"statusCode": 200,

"headers": {

"Vary": "Origin,Accept-Encoding",

"X-Frame-Options": "SAMEORIGIN",

"Strict-Transport-Security": "max-age=63072000; includeSubdomains; preload",

"X-Cache": "Miss from cloudfront",

"X-Amz-Cf-Pop": "DFW56-P1",

"X-Amz-Cf-Id": "Jo1GzdsXyLwoO__lWIXWWj6MlMyvx2EYcpgs0R0Vgxo0gi8Ufi4tLg==",

"Timing-Allow-Origin": "*",

"x-ms-apihub-cached-response": "false",

"x-ms-apihub-obo": "false",

"Date": "Mon, 17 Apr 2023 21:55:22 GMT",

"ETag": "W/\"5b-Mp2PQ3TXpicAGnrU8UOXH5yC4vQ\"",

"Via": "1.1 2685f5b632da4ffa2ee376ec1418d378.cloudfront.net (CloudFront)",

"Content-Length": "91",

"Content-Type": "application/json"

"body": {

"error": {

"message": "Missing required parameters: \"token\"",

"code": "001"

"success": false

}

I originally thought it was because of my organization's login credentials expiring and that I needed to refresh my connections every week. This seemed to have worked for a few weeks, but started happening again. So that theory went out the window. Please help. Thank you.

Bill

Vind meer berichten getagd met

Accepted answers

All comments

CarlisleHaworth1

Hi Bill, I am also experiencing this recently and not sure how to troubleshoot it. I had different errors manually generating feature reports today as well, but eventually got past that. I am going to reset my Survey123 connection in PowerAutomate to see if that is related to the token error, but will be following your post in case a solution is found.

AleSym

Hi everybody,

I have the same problem. Is there a proper solution for getting always a valid token for these connectors?

Thank you in advance

Alexander

KenBouchard

Same here, since yesterday, I'm getting the : "Missing required parameters: \"token\"" error on a flow using the S123 create report action.

Any clue anyone?

Thanks,

Ken

LisaMondt

Hello,

I'm having the same issue. The flow was working fine then last week started giving the: "Missing required parameters: \"token\"" error on a flow using the S123 create report action.

Has anyone found a solution to the problem?

Thanks, Lisa

Jamie_Leitch_CNF

I am having the same issue. Any solutions yet?

Martin-E1

I'm also having this same issue. It is really frustrating. I originally found the solution was to edit the Survey123 connection and sign back in every 2 weeks and this kept it going, however as of today that no longer seems to work and my flow is repeatedly failing at the create report step.

Did anyone find a solution to this?

Jamie_Leitch_CNF

This post solved it for me, starting from point #2: https://community.esri.com/t5/arcgis-survey123-questions/changes-to-survey123-connector-in-power-automate/m-p/1296406/highlight/true#M49737

NourSalamJMT

Same issue but in ArcGIS Enterprise with a custom Survey123 connector.

BenCapell_NWTF10

I had the same problem. The 'Create report' did not fail in the flow but it effectively was the point of failure because an error code was output and no report url was able to be transferred to the 'Upload file from URL' action. @BarbaraWebster1 I saw that you provided the solution to a related issue. Can you help here?

Background: I setup a flow to send an email with the survey report about 2 weeks before the first submission. After multiple tests the flow was configured to provided the intended result.

Issue: That first submission resulted in a failure (image below). An error code was output indicating a token was missing. No report was generated so no url was passed to the next flow action.

Workaround: I had to delete the Survey123 Connection used in the flow in the flow management page, add a new connection, then link to the new connection in the flow editor page.

Seeking a resolution: It seems as though something in the Esri/Microsoft authentication interface changed from when I setup the flow that caused the failure. The stakeholders that I set up the survey for need to be notified of the submission. So reliability on the connection and flow is important for us to continue using this ArcGIS functionality. Can I be notified of a faulty connection so I can reset it prior to receiving a failed flow email?

CarlisleHaworth1

If it's related to the token, you can usually just reset the S123 connection by choosing "switch account" and just log back in. I have this on my work calendar and do it every week. I've also read that using the ArcGIS connector instead of S123 avoids the issue altogether, but I have not verified this myself since i'm reluctant to switch up the internal workings of flows that work well apart from the token.

unregistered-user

I am having the same issue. Would prefer a 'set and forget' solution rather than a temporary fix.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.