Accepted Solutions
Amazing, thank you for that @abureaux !
I did end up going another way with it for the Create Report action and I THINK this should work too? A little simpler because I can work with dynamic content instead of the whole JSON.
I initialized a variable reportSuccess and in a Scope (Try) I added a Do Until where the Create Report runs, and then updates the variable based on the jobStatus return, so it will run until it is esriJobSucceeded
I then included the rest of my actions in the Try, and the last step I have outside of the Try is Send an Email with the Configure run after set to failed, skipped or timed out.
I also have the reportError variable which just accepts the body of the return from Create Report and puts it in a text file attachment to my email. My only issue with that right now is it doesn't retain any structure so it's just a big block of text. I'd love to parse the return for the error messages themselves, but it looks like the return changes depending on what happened so I'm not sure how to do that with consistency.
I also added a direct link to the flow run that failed in my email so that's super handy, and maybe easier.
I have a large number of Power Automate flows generating reports for my surveys constantly. Errors are rare, but not unheard of. And as you pointed out, simply rerunning the flow will have it succeed.
You mentioned that Create Report was successful, but then also mentioned that there was an error in that step. Are you using Esri's Power Automate Action, or is this a custom flow? If this is Esri's, I have never used it. If this is a custom one, what does your Do Until step look like? To generate a report, you will be waiting for the server to "finish" generating the report and will want the loop to look like this:
@or(equals(variables('jobStatus'), 'esriJobSucceeded'), equals(variables('jobStatus'), 'esriJobPartialSucceeded'), equals(variables('jobStatus'), 'esriJobFailed'))This step failing is where I see 100% of these random errors. In fact, I had a flow fail just this morning:
(It automatically reran and was successful)
In my case, I have error handling set up in the flow. Basically, if there is an error, the flow will reset and run again. I have never seen one of these mystery errors happen more than once in a row, and only at a frequency of every (very rough guess) 1/50 to 1/100 submissions.
Honestly, if you are experiencing the same thing as me, I don't think Esri support can help. The errors are far to transitory to analyze. I would suggest going the same route as me with the multi-stage report generation.
Thank you!
I am using the Esri Create Report action that they put out this year, so I just have that action in the flow itself. I do not have a "Do Until" in my flow at this point in time, but I think that will be the approach I take to avoid this issue, so I do really appreciate the example you included!
So basically the Action still runs and gives the little green checkmark saying it worked, it returns status code 200 either way at the end.
For sure. The Do Until step I am using should work with this Esri Action, based on what I am seeing in the JSON output. But there are things I do before this to set it up, so there will need to be tweaking one way or another to get this to work in your set-up.
For context, I believe the Esri Create Report Action would be the equivalent of my "HTTP - Create Report" step:
Here are the components (starting at the first Parse JSON):
1. Parse JSON - Job ID + Job Status
Body = The previous "HTTP - Create Report" in my first screen cap (so, probably your Esri Create Report Action?)
Schema =
{
"type": "object",
"properties": {
"jobId": {
"type": "string"
},
"jobStatus": {
"type": "string"
},
"submitted": {
"type": "integer"
},
"resultInfo": {
"type": "object",
"properties": {
"title": {
"type": "string"
}
}
},
"inputInfo": {
"type": "object",
"properties": {
"jobType": {
"type": "string"
},
"parameters": {
"type": "object",
"properties": {
"featureLayerUrl": {
"type": "string"
},
"queryParameters": {
"type": "object",
"properties": {
"objectIds": {
"type": "string"
}
}
},
"templateItemId": {
"type": "string"
},
"portalUrl": {
"type": "string"
}
}
}
}
},
"success": {
"type": "boolean"
}
}
}
2. Set variable - jobId
Value = jobId from the previous Parse JSON
3. Do Until - Create Report Job Finished
3a. Do Until's Logic. Must be entered in Advanced mode.
@or(equals(variables('jobStatus'), 'esriJobSucceeded'), equals(variables('jobStatus'), 'esriJobPartialSucceeded'), equals(variables('jobStatus'), 'esriJobFailed'))
3b. Delay - 5 seconds (Get jobStatus)
Simply a 5 second delay. This helps the Loop run smoothly.
3c. HTTP - Get jobStatus
This one will be interesting... JobId you already have from above. But Token I set previously. Not sure how to best accommodate that.
3d. Parse JSON - Result Info
Body = Previous HTTP step
Schema =
{
"type": "object",
"properties": {
"jobId": {
"type": "string"
},
"jobStatus": {
"type": "string"
},
"submitted": {
"type": "integer"
},
"completed": {
"type": "integer"
},
"resultInfo": {
"type": "object",
"properties": {
"title": {
"type": "string"
},
"totalCount": {
"type": "integer"
},
"resultFiles": {
"type": "array",
"items": {
"type": "object",
"properties": {
"objectIds": {
"type": "array",
"items": {
"type": [
"integer",
"string",
"number"
]
}
},
"name": {
"type": "string"
},
"size": {
"type": "integer"
},
"url": {
"type": "string"
}
},
"required": [
"objectIds",
"name",
"size",
"url"
]
}
},
"succeededObjectIds": {
"type": "array",
"items": {
"type": "integer"
}
},
"failedObjectIds": {
"type": "array"
},
"details": {
"type": "array"
}
}
},
"inputInfo": {
"type": "object",
"properties": {
"jobType": {
"type": "string"
},
"parameters": {
"type": "object",
"properties": {
"featureLayerUrl": {
"type": "string"
},
"queryParameters": {
"type": "object",
"properties": {
"objectIds": {
"type": "string"
}
}
},
"templateItemId": {
"type": "string"
}
}
}
}
}
}
}
3e. Set variable - jobStatus
Value = jobStatus from previous Parse JSON step.
4. Condition - Job Succeeded or Failed
This Condition is probably the most important part. If the report doesn't print, it goes to the If no branch, which resets the flow. If the report does print, it hits the If yes branch, and does whatever the next steps are.
Amazing, thank you for that @abureaux !
I did end up going another way with it for the Create Report action and I THINK this should work too? A little simpler because I can work with dynamic content instead of the whole JSON.
I initialized a variable reportSuccess and in a Scope (Try) I added a Do Until where the Create Report runs, and then updates the variable based on the jobStatus return, so it will run until it is esriJobSucceeded
I then included the rest of my actions in the Try, and the last step I have outside of the Try is Send an Email with the Configure run after set to failed, skipped or timed out.
I also have the reportError variable which just accepts the body of the return from Create Report and puts it in a text file attachment to my email. My only issue with that right now is it doesn't retain any structure so it's just a big block of text. I'd love to parse the return for the error messages themselves, but it looks like the return changes depending on what happened so I'm not sure how to do that with consistency.
I also added a direct link to the flow run that failed in my email so that's super handy, and maybe easier.
