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 have divided the tools into synchronous and asynchronous. In the asynchronous tools, it will call the API interface. Since these API calls will only return an operation number after completion and require waiting for an asynchronous callback, I need to continue with the subsequent actions after receiving the callback results in another API interface that receives the callback. How should I achieve this? I think I should bind the operation number with the thread_id after the asynchronous tool is executed, and then read the thread_id bound to the operation number in the API interface that receives the callback to continue executing the previously interrupted graph.
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.
-
I have divided the tools into synchronous and asynchronous. In the asynchronous tools, it will call the API interface. Since these API calls will only return an operation number after completion and require waiting for an asynchronous callback, I need to continue with the subsequent actions after receiving the callback results in another API interface that receives the callback. How should I achieve this? I think I should bind the operation number with the thread_id after the asynchronous tool is executed, and then read the thread_id bound to the operation number in the API interface that receives the callback to continue executing the previously interrupted graph.
Beta Was this translation helpful? Give feedback.
All reactions