brett11/10/2020, 5:56 PM
Chris White11/10/2020, 6:19 PM
to gracefully handle reruns / retries; this means that if you are triggering the same flow with this task, only one run will get created. To alter this behavior, you’ll need to provide your own idempotency key to the
method of your tasks. Note that you’ll want this key to change with each new run of your main Flow, so you might need to introduce a new task that generates keys for each run.
brett11/10/2020, 9:18 PM
is generated. That key is passed to each FlowRunTask. Because I'm calling the same child flow twice (despite receiving different parameters), both runs receive the same key. The worker agent completes one of these flow instances and then serves the cached result for the second run. So the solution would be to create two key generation tasks that sit as predecessors to the ADF flow runs? That would ensure a unique key is generated for each ADF FlowRunTask? FYI: This parent flow runs every 24 hours