Building JSON error handling

[JakePemberton]

Hi

I'm trying to catch an error flow (saw a good example here in a post last week which I tried to follow).
Below is the composed JSON

This is just an example of a flow. There could be a lot more steps, but I need the message + also the name of the step where the first message is in. So the first one where it fails.
I
So in this case that would be 

"name": "Update"

"message": "Bad Request - Error in query syntax."

Anyone an idea if this can be achieved?
Parse JSON is not an option I think as I want to make this reusable for other flows as well and the steps will be different.

[
    {
        "name": "Condition",
        "inputs": {
            "expressionResult": false
        },
        "startTime": "2023-11-21T16:58:39.3722936Z",
        "endTime": "2023-11-21T16:58:39.3744132Z",
        "trackingId": "8c911fe6-b9d0-47f7-8088-7adcae0fb036",
        "clientTrackingId": "08585013892102671082682253129CU144",
        "clientKeywords": [
            "testFlow"
        ],
        "status": "Succeeded"
    },
    {
        "name": "Update",
        "inputs": {
            "host": {
                "apiId": "subscriptions/3a3c8f3a-b051-4389-add3-35f0cadf681c/providers/Microsoft.Web/locations/westeurope/runtimes/europe-002/apis/commondataserviceforapps",
                "connectionReferenceName": "shared_commondataserviceforapps",
                "operationId": "UpdateRecord"
            },
            "parameters": {
                "entityName": "accounts",
                "recordId": "Testaccount"
            }
        },
        "outputs": {
            "statusCode": 400,
            "headers": {
                "Cache-Control": "no-cache",
                "x-ms-service-request-id": "faa0406c-7751-4808-a682-ecebf0961f47,b82a865d-cd24-4893-960f-71b69a6f1b4e",
                "Set-Cookie": "ARRAffinity=42c3fe55459896d66940089b6ee2813436511067a378da57ae5b0812018c1f4215134d20c556b0b34b9b6ae43ec3f5dcdad61788de889ffc592af7aca85fc1c508DBEAB74CFD4D16159460048; path=/; secure; HttpOnly,ReqClientId=7bc1208e-7671-4e85-80e1-e055e164835d; expires=Tue, 21-Nov-2073 16:58:39 GMT; path=/; secure; HttpOnly,ARRAffinity=42c3fe55459896d66940089b6ee2813436511067a378da57ae5b0812018c1f4215134d20c556b0b34b9b6ae43ec3f5dcdad61788de889ffc592af7aca85fc1c508DBEAB74CFD4D16159460048; path=/; secure; HttpOnly",
                "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
                "REQ_ID": "b82a865d-cd24-4893-960f-71b69a6f1b4e",
                "CRM.ServiceId": "framework",
                "AuthActivityId": "b1a6280d-d81e-49ba-a83d-5b719ac74adf",
                "x-ms-dop-hint": "4",
                "x-ms-ratelimit-time-remaining-xrm-requests": "1,198.87",
                "x-ms-ratelimit-burst-remaining-xrm-requests": "7996",
                "OData-Version": "4.0",
                "X-Source": "221173246158230105901131912168154115120421812441386213712935159134818524773123735229,9176161242139420420213993493223518013014249371431123255838118226151239243105124",
                "Public": "OPTIONS,GET,HEAD,POST",
                "Date": "Tue, 21 Nov 2023 16:58:39 GMT",
                "Allow": "OPTIONS,GET,HEAD,POST",
                "Content-Type": "application/json; odata.metadata=full",
                "Expires": "-1",
                "Content-Length": "80"
            },
            "body": {
                "error": {
                    "code": "0x80060888",
                    "message": "Bad Request - Error in query syntax."
                }
            }
        },
        "startTime": "2023-11-21T16:58:39.3756439Z",
        "endTime": "2023-11-21T16:58:39.4930473Z",
        "trackingId": "04756ad7-7e7f-4b7f-8099-558b5200b7e5",
        "clientTrackingId": "08585013892102671082682253129CU144",
        "clientKeywords": [
            "testFlow"
        ],
        "code": "BadRequest",
        "status": "Failed"
    }
]

[VictorIvanidze]

Just use "Filter array" action.

[JakePemberton]

Could you provide an example on how to do this for this one?

[grantjenkins]

Here's an example of "hopefully" what you're after.

See full flow below. I'll go into each of the actions.

In my Scope I've got two actions. The second action uses the following expression which will cause a divide by zero error.

div(100, 0)

I then have a parallel branch that handles the success or failed branches.

The Compose Success is set to run when the flow "is successful".

The Filter array is set to run when the flow "has failed".

The Filter array uses the following expressions to extract out the object that contains the failed details.

//From - looks at the result of my Scope called 'Scope'
result('Scope')

//Condition
item()?['status']

You can then use the following expressions to get the Name, Code and Message from the action that failed.

//Name
first(body('Filter_array'))?['name']

//Code
first(body('Filter_array'))?['error/code']

//Message
first(body('Filter_array'))?['error/message']

If I run my flow, I'll get the following output.

Name: Compose_Div_Error
Code: InvalidTemplate
Message: Unable to process template language expressions in action 'Compose_Div_Error' inputs at line '0' and column '0': 'Attempt to divide an integral or decimal value by zero in function 'div'.'.