I love the new Todo solution, I think itâs great!
I was running a few test as i am planning to move over to the Todo form the Approval links pieces. But I noticed the following.
I think there is missing some data for the âCreate Todo and Waitâ and âWait for approvalâ part. The âTodo and Waitâ piece isnât showing a task ID. which is needed for the âwait for approvalâ, Could you please look into this?
Also I would recomment changing the name âwait for approvalâ to âwait for reponseâ as i can assume if an invoice is not approved you would like to follow a different flow.
Please let me know when this is resolved so I start investigating further
Create Todo and Wait are designed to work together as a single piece (Create Todo + Wait for Approval), where the output is the result of the approval response.
On the other hand, thereâs another strategy called External Channel, which separates the flow into two distinct pieces: one for creating the todo and another for waiting (by ID) for the response.
For renaming âWait for Approvalâ to âWait for Responseâ, I will send you feedback to the team.
Thanks for the reply! there was no example output to work with in the piece, but i think itâs fixed in the mean time.
I ran into another issue, could you please look into this? I am getting a 400 error, but not sure what the reason is. Please let me know if any other details are required from my end.
I was having a similar issue with the Todo piece, and it seems that deleting the old one and replacing it with a newly created one fixed the issue for me.
Not sure if it will work for you, but that is what I did to get things going again.
As a side note, I had also spun up and tested an Approvals Link creation piece before I removed and added the new ToDo piece. So, if you arenât having luck with just replacing it outright from the start, this may be something else to try.
Thanks for the suggestion, i have tried it too but still no working perfectly, I noticed sometime issues are related to flows, like some memory is there. I have a workaround for now and as soon as I find time to recreate the flow i will probably do so.
Iâm sorry to hear that it didnât work for you.
As a final suggestion, which you might have already tried, I experimented a bit more and created a duplicate of the workflow that wasnât working. However, simply duplicating it did not resolve the issue. It was only after I created a new ToDo item within the duplicate that the problem was fixed.
So, if you havenât already attempted this, it may be worth trying. This method might eliminate the memory retained by the non-working flow.