I think I've found a bug where CCI projects can't have a flow with an asynchronous path.
I'm still confirming to my satisfaction that this is replicable, and I don't know if it's a CCI problem or an SFDX problem. Steps to reproduce:
1. Create a scratch org.
2. Build a flow (mine's on Opportunity) that has an asynchronous path. (This, of course, requires entry criteria for "only when the record is updated to meet conditions.) Leave the default that you're building in auto-layout.
3. Put something on that async path. (I have a Get Records element.)
4. Save the flow.
5. Download the flow to your repo (cci task run retrieve_changes)
6. Spin up a new scratch org that includes with your project and the flow we just built.
7. Open the org in the browser and go into the flow.
8. Notice that the flow is now in freeform layout. And the asynch path doesn't exist. And your flow element isn't attached to the Start element. And you get an error warning that nothing is connected to the Start element.
Definitely replicable for me.
Also (in #8) if you go into the start element, the slider for Add Asynchronous Path is actually turned off.
