Export flow from one environment, import flow into another environment and flow is not working

[tvd_nzi]

because the flow status is "off".

Why? The exported one in the dev environment was never deactivated, every other import didn't touch the status of the flow but since today flows are deactivated when imported into another environment. Is this really by design? Anyone else encountered this?

Deployed a build release with "publish workflows" checkbox marked. So can't find any other settings.

[tvd_nzi · Accepted solution]

Nevermind, turning on the flow threw an error telling me CDS connection is missing. The flow previously was a flow with standard actions and triggers which I turned into a CDS flow. Error handling could be improved but that was the issue and could be resolved. Still after deployment I set the connections and there were no errors thrown.

Failed to activate component(s). Flow client error returned with status code "BadRequest" and details "{"error":{"code":"FlowMissingConnection","message":"The flow is missing a connection for api 'shared_commondataservice'. Reauthenticate the connection or remove from the flow and re-save."}}".