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!
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: Polaris specific Use case: In classic we stage lists to only have the nodes with numbers being created (e.g. Customer_account) to…
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: As a Product Owner, I spend a lot of time in our different workspace environments updating various configurations, entering data,…
Following on from the below thread, https://community.anaplan.com/discussion/161787/nux-show-history-missing-changes-vs-classic Problem: Cell history in NUX is incomplete and does not include all changes resulting from imports/processes, causing gaps in auditability and confusion amongst users when they don't know why…
