Hi Steve,
I have loaded your flow and will look deeper.
I really need to run this in the 'real world' to see what is happening. But like all these closed loop systems, things rely on other things over which we have no control, to either happen, or not happen!
As to what the flow does, I tried to explain in my first post, just not very well.
If some InfluxDB data obtained from an API is not available at a certain time, I need to trigger a fetch from the same API until the data does become available and is stored in the InfluxDB. Once the data is available, I need to stop accessing the API and also send an email with some of the accessed data in. This happens once a day and so the process starts again at the same time the next day.
This is all part of a far more extensive flow, just trying to keep things simple for developing the flow.
As I mentioned, my concern was that this might be a problem in beta.3 but gladly it seems not, so I am happy. I will carry on experimenting adding your tips into my flow. As ever, the pointers and tips are much appreciated. Even going to add the Context Data flow you gave me before to help me understand.
Thanks for the comments in the function! Very helpful for me!!
