Some of the Sync Flows in the CoE Starter Kit have failed.

[O365Support]

Does this bug already exist in our backlog?

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

Describe the issue

SYNC SYNC HELPER - Cloud Flows

Error
Action 'See_if_already_in_Maker_Table' failed

Expression expected at position 17 in 'admin_makerid eq '.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.7

What app or flow are you having the issue with?

SYNC HELPER - Cloud Flows

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

[mohamrizwa]

Hi @O365Support,
Thank you for reporting this issue.

I have identified the root cause and recommend you to update the value as shown below:
Before:

After:

Once this change is applied, the flow should function correctly. These updates will be included in the next release.

[O365Support]

Thank you for the update is there any workaround until next release as if we edit the flow it will create unmanaged layer

[mohamrizwa]

Hi @O365Support,
For now, I kindly suggest updating the flow. Once this fix is released, you can upgrade to the latest version. Before upgrading, please remove the unmanaged layer from this flow.

[jackpoz]

FYI after updating the flow in the "Get Owner Details" scope, it fails further below in the "Upsert Flow Details" section:

[mohamrizwa]

Hi @jackpoz,
Please debug the update action to determine where the incorrect data is coming from.

[jackpoz]

It's the same root cause that propagates further down after applying the change from null to "" you mentioned.

The action in my screenshot uses the output of IsOrphan action that is not set to true when owner is "". You will have to use a variable and set it to true in the branch of "If owner is null" when it's true.

I would strongly recommend to test this in your development environment or it will take months before all cases are properly taken into account, or restore the previous version that worked fine.

[O365Support]

Hi @O365Support, For now, I kindly suggest updating the flow. Once this fix is released, you can upgrade to the latest version. Before upgrading, please remove the unmanaged layer from this flow.

Hi @mohamrizwa ,Post verification ,the reported bug is not fixed in latest version of COE i.e. -CoE Starter Kit January 2026.It is still open ,kindly suggest.

[mohamrizwa]

Hi @jackpoz,
Please debug the flow, identify the action where it is failing, and share a screenshot for further investigation.

[jackpoz]

Are you a bot ? I already wrote here #10631 (comment) .
I even wrote the solution to fix it.

Can Microsoft please re-hire the people that used to manage CoE Starter Kit ? The quality of this tool has fallen a lot in the past months.