You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked the Langflow documentation and I haven't found a proper answer for my problem. My use case is I want to run a flow in the background, and I want to get back a job id or request id or something, what I can use to query the result of the flow when it finish the run.
I am using the webhook endpoint to be able to do it, it is perfect for the call, because it runs in the bg, but in the end I can not identify the exact result in the messages table, or in the GET messages API call.
It would be great to return back the job id when I call the request, and when the flow finish the run, I can call the get message endpoint to be able to query the result.
What do you think about it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've checked the Langflow documentation and I haven't found a proper answer for my problem. My use case is I want to run a flow in the background, and I want to get back a job id or request id or something, what I can use to query the result of the flow when it finish the run.
I am using the webhook endpoint to be able to do it, it is perfect for the call, because it runs in the bg, but in the end I can not identify the exact result in the messages table, or in the GET messages API call.
It would be great to return back the job id when I call the request, and when the flow finish the run, I can call the get message endpoint to be able to query the result.
What do you think about it?
Regards,
Istvan
Beta Was this translation helpful? Give feedback.
All reactions