Based on this Known Issue it looks like the ISCLONE() function isn’t supported in debugging entry criteria? Is this the final word on this?
Assuming the reasoning behind the Trigger Order functionality is accurate, then having a decision check after a flow initializes is not the same as handling in entry criteria. When building and testing flows we need to be able to test the design, not something “close enough”.
Hi Sean,
Yes, the Known Issue indicates that ISCLONE() in the Start/entry criteria of a record-triggered Flow cannot be used with Flow Debugging. The limitation is specifically with debugging the flow when ISCLONE() is part of the entry criteria.
And I agree that moving the check into a Decision element isn't exactly equivalent—the flow has already started, so it doesn't test the same entry-condition behavior.
For testing, one workaround is to temporarily move the ISCLONE() logic into a Decision element while validating the rest of the flow, then restore it to the Start criteria. For the actual platform limitation, I'd also keep an eye on the Known Issue for any status/update from Salesforce.
