[CoE Starter Kit - BUG] Audit Logs - ContentID returned not being recognized

[NicoleSSmith]

Does this bug already exist in our backlog?

• [X] I have checked and confirm this is a new bug.

Describe the issue

Admin | Audit Logs | Sync Audit Logs (V2) is failing. When I navigate to the Flow Instance URL, getting the follow error:

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.11

What app or flow are you having the issue with?

Admin | Audit Logs | Sync Audit Logs (V2

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

AB#558

[pete-msft]

@mrmonto1 you should not need to restart the subscription when upgrading CoE Kit. Subscription is not stopped automatically when you upgrade the solution

[mrmonto1]

Hi @pete-msft . That's good to know. However, speaking from my experience after successfully installing the COE (July release) and setting up the Audit Log subscription (or at least I thought it was successful because I received a 200 response when instantiating it), I didn't turn that flow off or stop the subscription prior to upgrading to the August and September releases. I had to re-instantiate the subscription to get the Admin | Audit Logs | Sync Audit Logs (V2) to work in the Sept. release.

[NicoleSSmith]

https://github.com/microsoft/coe-starter-kit/issues/6248#issuecomment-1707157759 @pete-msft in regards to the above comment, I ran the script with the values of the ParseContentIDs

I edited Admin | Audit Logs | Sync Audit Logs (V2), added the compose action after ResetHttpCallFailed2. Then grabbed the URL from the output and ran the URl through the script you attached and this is my result:

The flow is still continuously failing. How do you suggest I proceed? Would upgrading the COE to the newest release help resolve the issue? We are currently on version 4.11, updated in July.

[pete-msft]

@NicoleSSmith Ok, so all those tests worked also the complete API URI which is used in the flow works in PowerShell script but still results same "Blob key..." error in the sync flow? Or is the flow failing now in some other action with different error? Yes, I recommend to upgrade anyhow to the latest version. The bug in the "Update Last Run Fail 2" action is fixed in September version https://github.com/microsoft/coe-starter-kit/issues/6480

BTW, I do not recommend to sent all outputs to the case as they contain usernames, so maybe good if remove the files. Should be enough to ma send screenshots of the output which does not contain any sensitive data

[pete-msft]

@NicoleSSmith hope you are doing well! Were you able to find time to upgrade to the latest CoE Kit version and test the audit log sync?

[NicoleSSmith]

@pete-msft I am well, Thank you. The flow was still failing at the blob key error. I have a working session scheduled for next week to get the newest upgrade installed. I will keep you updated on the progress.

[NicoleSSmith]

I was able to update to the October release after working through bug https://github.com/microsoft/coe-starter-kit/issues/6018. I am no longer seeing this issue.