amararama
Use a table action to trigger a long running flow
Hi all,
Just wondering if there is a recommended way to use table actions to trigger a flow that I dont need to see a response from during the lifetime of the session.
I have a table with various params, that when triggered will upload some folder to S3.
Now, the flow triggers in the background as an independent run, but the table still seems to wait for a response before its state is updated.
I'm wondering if theres a way to have the flow trigger and return something along the lines of a 200: OK, and let the flow continue, in the event of an error I can build my own error handling into the flow, but I dont want it to choke up the table if the user wants to run multiples of this process from the table.
I assume the way to do this would potentially be to call the flow from the hook as opposed to directly from the button?
4 replies