which kind of works, however the UI is still counting the duration as if it was still running...
k
Kevin Kho
07/27/2021, 8:40 PM
Hey @Andre Muraro, what is the use case of making it Skipped at the end of the Flow? I think at that point the flow has already suceeded so what are you skipping?
a
Andre Muraro
07/27/2021, 8:48 PM
@Kevin Kho basically I have an api which I have to periodically ping to check whether it has new data for me. If it doesn't, I skip all processing. However the business side demands that I hit that api very frequently, which makes it a little hard to figure out which flow runs actually found data and which didn't, at a glance. So my idea was to cause flows to show as skipped, so as to easily distinguish them from the ones that actually found data to process.
k
Kevin Kho
07/27/2021, 8:51 PM
Ahh I see. What you have there looks right to me. Let me see if this there is a better way to do it.
Kevin Kho
07/27/2021, 9:10 PM
Chatted with the team and there’s a bunch of reasons why the duration keeps going up (there is no end date when SKIPPED). I think the only thing we can recommend here is to use ENDRUN instead to end the flow run. You can also raise SUCCESS with a message and maybe filter by the message?
a
Andre Muraro
07/27/2021, 9:15 PM
Think I'm not familiar with this ENDRUN method. Got any docs on it?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.