Flows with CDS (current environment) trigger will not trigger if...

[mike_mcguinness]

Hi everyone, I have run into an odd problem with multiple flows not running in a new environment.  This includes imported flows, as well as new flows created from scratch.

I am using the "Common Data Service (current instance)" trigger "When a record is created, updated or deleted", with an "Update" trigger condition.  I have recreated the trigger, the connection, created new test flows from scratch.

The flows will only trigger if "Filtering attributes" and "Filter expression" are left blank.  If either has values, the flows will never trigger.  The same flows work fine in other environments.

Any ideas?

[mike_mcguinness]

FYI, looks like this is an issue with CDS updates not triggering when File fields are changed in our new environment.  Works fine in our old environment. Both are 2020 release wave 1. MS support is investigating.

[ManishJain]

Hi @mike_mcguinness,

Please add compose step after the trigger and add the input as your attribute to see whether it is really getting updated.

Thanks

[mike_mcguinness]

Hi @ManishJain, we know the file field is updated (we can retrieve and process it in the flow), but the flow has no run history when the file field is added as a filter. So we know that changes to the file field are not triggering the flow in this environment.

[ManishJain]

Hi @mike_mcguinness ,

Now that your flow is running without any attributes in place as well as conditions, why not save the record with Attribute getting changed. 

In compose action view your attribute if it is really changed. 

Thanks