[CoE Starter Kit - BUG] SYNC HELPER – Cloud Flow Incorrectly sets Orphaned Flows as Not Orphaned

[dtegg]

Does this bug already exist in our backlog?

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

Describe the issue

The Flow "CLEANUP - Admin | Sync Template v3 (Orphaned Makers)" runs on a weekly basis & marks all Orphaned Makers objects as Orphaned. We've discovered that there's a bug in "SYNC HELPER – Cloud Flow" - under the "Get Owner Details" scope, the "Get_Maker" action attempts to retrieve the Maker & if successful, the next 2 actions are skipped. The "catch for orphans no id" action runs if Get Maker fails, but the IsOrphan action is only running if the "catch for orphans no id" action runs.

Therefore even if the admin_makerisorphaned parameter for the Maker is true, it doesn't evaluate the expression in the IsOrphan action, so then further down the Flow (in the Upsert Flow Details scope) it checks if the output of IsOrphan is True and given that it didn't evaluate previously, it will always go down the false path. As such it sets the Flow is Orphaned parameter to No incorrectly.

Expected Behavior

We've checked the corresponding Flow for Apps (SYNC HELPER - Apps) and that has the Configure Run After setting on IsOrphan to Successful AND Skipped, whereas in "SYNC HELPER – Cloud Flow" it is just Successful.

We've changed SYNC HELPER – Cloud Flow to match the SYNC HELPER - Apps - configured run after on IsOrphan to be Succesful and Skipped and it seems to have solved the issue. When SYNC HELPER – Cloud Flow now runs against Flows that have already been marked as Orphaned they don't now get set as Un-Orphaned.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.8

What app or flow are you having the issue with?

SYNC HELPER – Cloud Flow

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Anything else?

No response

[dtegg]

[AmarSaiRam]

Hi @dtegg
Thanks for reporting this!
Check with these changes once
SYNC HELPER – Cloud Flow incorrectly marks flows as not orphaned when their maker has admin_makerisorphaned = true. The IsOrphan action was skipped when Get_Maker succeeded, preventing evaluation of the maker's orphan status.

Changes
Updated IsOrphan action's runAfter configuration to trigger on both Succeeded and Skipped statuses
Aligns with existing implementation in SYNC HELPER - Apps
"IsOrphan": {
"runAfter": {
"catch_for_orphans_no_id": [

• "Succeeded"
  

• "Succeeded",
  

• "Skipped"
  

  ]
  }
  }
  When Get_Maker succeeds, catch_for_orphans_no_id is skipped. IsOrphan now evaluates regardless, checking admin_makerisorphaned from the retrieved maker record.

[AmarSaiRam]

Dear User,

We noticed that this issue has been pending for quite some time, and we have not received any recent updates from your end. In the absence of further communication, we are proceeding to close this ticket, assuming that your concerns have been addressed or resolved.
If you continue to experience any difficulties related to this matter, please feel free to open a new support ticket. This will help us ensure prompt and effective assistance, rather than reopening the new Issue.
Thank you for your understanding and cooperation.

Best Regards,
CoE Starter Kit Team