Running "side effects" in flow / return early to (windmill) App
I'm having a use case that I think is not normal maybe, but not unheard of at least. But I'm not sure how to model it in windmill.
I have a (windmill) app that runs a flow, the flow inserts into a database, and then it notifies about this a couple of places (slack, email).
What I would like to achieve is to return a result o the user after I have inserted into the database, and then let the flow do slack and email afterwards.
so the user do not need to wait on this result. The only way I see doing this now, would be to call another flow from the HTTP endpoint... but that feels a bit hacky since I now can't see the relation between the flows.
is it a better way of modelling this I do not see?
I have a (windmill) app that runs a flow, the flow inserts into a database, and then it notifies about this a couple of places (slack, email).
What I would like to achieve is to return a result o the user after I have inserted into the database, and then let the flow do slack and email afterwards.
so the user do not need to wait on this result. The only way I see doing this now, would be to call another flow from the HTTP endpoint... but that feels a bit hacky since I now can't see the relation between the flows.
is it a better way of modelling this I do not see?
