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

[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.