ArneV.24073 (Cloudworks AS) asked a question.
Problems with activating workflows mirgrated from other tenant
I have created a set of workflows on one of our tenants, which I have exported and then imported into one of our other tenants, However, when I try to activate them, one of three things happens
- Workflows is acivated (no problem with that 🙂 )
- Activation fails with message "First connect to your apps"
- Activation fails with message "Could not activate Flow"
With regards to the second on there; as far as I can tell, I've checked that any retrieval of user data etc has been updated to use the importee tenant's Okta connection, and for some of the workflows this happens too, they aren't even using any app connection.
Is there any place we can check for more info/details about this? As far as I can tell, this isn't tracked in the regular system log.
Anyone experiencing similar problems? Any advice on how to get them sorted out?
Hi Arne,
For the second item, when you connect flows in different orgs, the cards need to have the connection reset (because it is no longer the same as original). Could also possibly be the HTTP connection (unsure in your case)? Should be able to scan the flow looking for the cards with red.
For the Activation fails with message "could not activate flow". This is due to a few different reasons, 1 the version of the card(s) is not the same between environment(s), there are functions/methods in the one environment and not the other. I have also experienced this one. The only way (currently) to resolve this one is to open the source environment and the destination environment and start to manually rebuild the flow in the destination. This will allow you to find which card/function is the issue and allow you to determine how to work around this.
If you still need more assistance please open a support case to allow us to continue working with you on this.
Hello, I too am experiencing the activation error. I did also recreate workflows and support case is opened but still no solution yet. I just wanted to know if you had any more findings on possible areas to check to get this resolved. The account for workflow and connections are assigned to okta workflows app and checked connections and reauthorized and they were successful and healthy. Also tried deleting and readding the event card in beginning of parent flow this was noted some other discussion and said it was resolved by doing so. But nothing has worked.
Can you please open a support case for us to work on this with you? Have you tried creating a new connector and switching the app cards to use that? Have you tried re-creating all of the app cards in the flow? Guessing this was due to export/import from one environment to another.
I'll do some more testing on this moving forward; we have a hub/spoke setup with many spokes, so having an easy, straight-forward way of migrating/updating these throughout the environment is essential.
Thanks for your feedback! 🙂