Power Automate is a very powerful tool for building no-code solutions, but no-code certainly doesn’t mean no complexity and occasionally errors arise which can be difficult to troubleshoot, especially when working with documents and arrays!
This short post is focused on some common issues but also details what information you should provide to our support team if you need to raise a ticket
Check the ‘INPUTS’ and ‘OUTPUTS’
Every action within Power Automate receives an input and generates an output. These are the first things to check when an action has failed, i.e. what data did the failed action receive and then generate? Thankfully, accessing this information is very simple.
1. Open your failed Flow’s run history and select the failed instance:
2. Locate the failed Flow and check the ‘Inputs‘;
2.a For smaller payloads the Power Automate interface will allow you to click 'Show raw inputs' which shows the complete dataset sent to the action:
Note: The Encodian support teams may request the 'Input' value, simply copy this data into to a TXT file and provide via email to the support team.
2.b For larger payloads the Power Automate interface will provide a 'Click to download link'
2.c Clicking the link will open a new browser tab containing the JSON data sent to the action. You may wish to install a JSON viewer extension to your browser as this will make it a lot easier to read the data.
Note: The Encodian support teams may request the 'Input' value, simply copy this data into to a TXT file and provide via email to the support team.
3. Scroll down to review the ‘OUTPUTS‘
3.b Most actions including the Encodian action will provide a meaningful error message within the body of the output. Make sure to check this value:
2. To review the complete dataset provided by the action click 'Show raw outputs'
Note: The Encodian support teams may request the 'Output' value, simply copy this data into to a TXT file and provide via email to the support team.
Encodian Error Messages
When an error occurs it is super important to review the error message which has been generated. The errors will provide a good glimpse as to what is actually happening.
"The response is not in a JSON format"
Power Automate will render some messages with a catch-all message of "The response is not in a JSON format", however the actual error message will still be present in the 'Body' of the output, so make sure to check this:
Unauthorized / Forbidden – 401 / 403 / 4** Status Code
This error means that the connector has rejected your authentication request, either because an invalid API key has been provided, or you have exceeded the number of actions permitted by your subscription:
Bad Request – 400 Status Code
This error means the data sent to the action has failed validation and has been rejected:
BadGateway – 502 Status Code
When an actual processing error occurs Encodian’s connector returns a 500 status code (Internal Server Error), however, Power Automate will automatically interpret 500 errors thrown by connectors as a BadGateway error before overlaying with a 502 status code.
The actual error generated by the Encodian action is contained within the ‘Errors’ property:
What data should I collate to raise a support ticket?
If you need to raise a support ticket with Encodian we’d highly recommend providing the following information where possible:
- The email address associated with your Encodian subscription (preferred) or current API Key.
A short description of your issue. - A short description of your use case. Sometimes there are alternative options but we can’t suggest them if we don’t understand your use case/requirements.
- An export of your Flow as a ZIP package; refer to the guidance found here
- The values from ‘INPUTS’ and ‘OUTPUTS’ of the failed action are attached as separate TXT files.
We hope this post provides some clarity on how to review and interpret errors you may occasionally receive and what information to provide our support team with so that we can best help you.
0 Comments