[BUG]: [Child] Admin | Sync Logs constantly failing

Description We are configuring CoE for the first time and the “[Child] Admin | Sync Logs” flow always fail.

Component

• Solution [CenterofExcellenceAuditLogs_1_3_2_managed]
• Version [e.g. 1.3.2]
• Flow [Child] Admin | Sync Logs

Steps to reproduce the behavior: Start the “Admin | Sync Audit Logs” and wait for it to fail. It turns out it is caused by its child flow.

Screenshots The “Admin | Sync Audit Logs” result

Few clusters of the “[Child] Admin | Sync Logs” always fail.

Parse JSON step output: [ { "message": "Invalid type. Expected String but got Null.", "lineNumber": 0, "linePosition": 0, "path": "[54].ResultStatus", "schemaId": "#/items/properties/ResultStatus", "errorType": "type", "childErrors": [] }, { "message": "Invalid type. Expected String but got Null.", "lineNumber": 0, "linePosition": 0, "path": "[54].ClientIP", "schemaId": "#/items/properties/ClientIP", "errorType": "type", "childErrors": [] },

The rest of the flow:

Any idea what is wrong? Thank you

[manuelap-msft]

Hello,

thank you, that’s great news - this won’t have an impact later on, the only fields we use to update the Audit Log table are these ones:

 "CreationTime": {
                "type": "string"
            },
            "Id": {
                "type": "string"
            },
            "Operation": {
                "type": "string"
            },
            "Workload": {
                "type": "string"
            },
            "AppName": {
                "type": "string"
            },
            "ObjectId": {
                "type": "string"
            },
            "UserId": {
                "type": "string"
            },
            "UserKey": {
                "type": "string"
            },

The ResultStatus field is not one we use.

The initial schema was put together based on a sample of an Audit Log event, under the assumption that the schema for Audit Log event is consistent. As that’s not the case, I’ll work on updating the Parse JSON schema to only require fields we use later on and remove all optional fields we don’t.

Thank you for your help in testing this!

[jazizka]

Hello Manuela, the flow executes successfully since last week. It is solved.

Thank you for your help, Jakub