This would be a very convenient option: start a step and not wait for it to finish. For example, I need to wake up the model that will be needed in step 7. It takes 30 minutes to wake up, so I have to start waking up in parallel with step 4.
Hi Golosov!
This idea would be useful for large integrations. It would be great if there was a setting where the developer could specify whether to wait for the step to complete or continue on. 👍️
Hi Razarenov,
Thank for the vote!
I am quite sure this is already somewhere on the roadmap
I'm so looking forward to it and trying to bring the moment closer
Thanks for sharing this feedback! Today the default behavior is that status controls the flow outcome.
The ability to configure when a flow should stop (or continue) based on Cloudworks termination status ("failures", "partial success") is on our roadmap.
Hello all, our recent launch includes the following capabilities (which maybe of interest to this thread):
1. Continuity of the flow can be configured based on a step's status, allowing more flexibility in constructing complex data flows 2. Step count of 20 per flow (increased from 10 per flow) to support longer chains. 3. Re-run flow from any step, allowing for ease of troubleshooting.
More details here:
https://help.anaplan.com/ee054c8c-6eb7-44af-8334-4136a15302fc-Manage-integrations-flow-steps
Hi @AshwinK, thanks for the update!
As an Anaplan Tenant Administrator, I need the Export functionality to be able to export all the existing Tenant Level Roles information as well as the role details, into a CSV file, So that I have the accessibility to document and report to my security team. I know this feature is successfully implemented when I can see…
Currently, only Workspace Admins in Anaplan can access certain model metadata and deployment validation panels (such as Revision Tags, Data Tags, etc.) in the Production workspace. For security and compliance reasons, we want to avoid granting admin-level access to users who only need to view this information. There is no…
Currently, Anaplan does not natively restrict number inputs to specific ranges. Users can input any numeric value, which may result in data integrity problems, especially in collaborative or decentralised planning environments. Introducing a validation capability—where model builders set upper and lower bounds for number…