Hi there
We are trying to use the GET /flows/<_id> API endpoint which is able to get details of a specific flow. After a successful run, the returned JSON object does not contain 'lastExecutedAt' in some flows. Especially starting with webhooks as source (export) tiles. Why is that? Any Idea?
Thanks
Can you please confirm if it is a branching flow or a linear flow?
Previously we applied branching, now we removed it. But it's still containing 1st matching branching.
Tharaka, just wondering if you've removed/deleted branches (not branching). In this case, when you've only one branch, it will look like a linear flow but will have the branching router icon with the default "First matching branch." See also, Manage branching in your flow.
Thanks for the reply
Yes, we removed branches, but still branching icon is there. Now we treat it as a linear flow.
Is that impact on not returning 'lastExecutedAt' in Flow API endpoints?
Tharaka, if you see the branching router icon, it means that it's treated as a branching flow – in this case, a flow with a single branch. If you want a linear flow (that is, no branching), you need to delete the branching.
I'm not sure whether this has an impact, but QA is trying to look into the matter.
Yes
We tried to delete the branch. If we delete the branch other tiles are also deleted with the branch. That's why we keep a linear flow with a single branching
@tharakaathukorala - For branching flows, the 'lastExecutedAt' is not returning in the response.
For linear flows tried with both Webhook and HTTP Export, 'lastExecutedAt' is returned in the response.
Can you please remove the branching and try to run the linear flow
Thanks for the comment, G Abhinash.
We removed the branching, but it still shows the branching icon. Is branching directly impact to not returning 'lastExecutedAt' in Flow API endpoints?
We can see the last run from the UI.
Why it is not returning from the GET /flows/<_id> API endpoint which is able to get details of a specific flow?
This is a bug with branched flows, and there is no work around other than rebuilding the flow without any branching at all.
Tharaka, I hope you are doing good!
Wanted to keep you posted the progress here, the fix for this bug is available in the production. Could you please try it out from your end. Thanks!
Thank you very much for your comments.
