Flow is triggering on wrong CDM

[Crazykarl7]

Hello,

 I have 2 Dynamics databases (1 production 1 sandbox).  I have a flow that will take data from the dynamics system and put them into a on-premise SQL server using the gateway.  Because I'm using the gateway I have the flow in the default environment.

The trigger for the flow is automatic based upon if a value in the lead is modified using the CDS connector. The trigger/connector is pointed to the production instance. When the sandbox is updated, the flow is triggering. Looking at the flow run, it says it's production. 

Sandbox is a restored copy of production.

Any ideas on how to get this to stop?  I have a copy of the same flow for sandbox to transfer data to a sandbox SQL server but my expectation is that the trigger will only be triggered for the environment specified in the flow.

[tfhegdbn]

Unsure if this is an issue, you can contact MS support to resolve your issue.

[Crazykarl7 · Accepted solution]

I think I fixed it. I changed the trigger to point to sandbox, saved it, and changed it back to point to production and saved it. That seems to have reset the connection so that it triggers on the correct DB.

[v-bacao-msft]

Hi @Crazykarl7 ,

Great! It appears that you have found a solution to your issue!

If so, please click "Accept as Solution" on the reply that describes how you were able to solve your issue!

Best Regards,