The fact that it worked on resubmit tells you the input to Parse JSON was different between the two runs. The schema was fine, the data was not.
Most common causes for intermittent Parse JSON failures in scheduled flows:
1. The previous action returned null or empty. If the action feeding Parse JSON returned nothing (empty response, no results, API timeout), Parse JSON has nothing to parse and fails. Add a condition before Parse JSON to check the input is not blank before attempting to parse.
2. The input sometimes returns a different structure. For example an API that returns a single object when there is one result but an array when there are multiple. The schema only covers one shape so it fails on the other.
3. Transient upstream failure. The source (API, SharePoint, HTTP call) had a temporary error and returned an error response instead of valid JSON. The resubmit worked because the source was back online.
try this to fix it:
- Add a Compose action before Parse JSON and log the output of the previous action so you can see exactly what was passed when it fails next time
- Wrap Parse JSON in a Scope block with Configure run after set to run on failure, and send yourself the raw input to inspect it
- If it is a transient upstream issue, add a retry policy on the action feeding Parse JSON
What action is feeding the Parse JSON and what does the schema look like? That will confirm which of these is the actual cause.
Best regards,
Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.
❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).
🏷️ For follow-ups @Valantis.
📝 https://valantisond365.com/
