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
Copy file name to clipboardExpand all lines: website/content/docs/core/micro.mdx
+46-1Lines changed: 46 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,4 +376,49 @@ When you call `MicroAgentica.conversate()` function, the agent will start the [#
376
376
377
377
If you want to archive the conversation state of current agent, store the returned prompts to your database with serialization to `IMicroAgenticaHistoryJson` format by calling `MicroAgenticaHistory.toJSON()` function. And then restore the conversation state by assigning the prompt histories to the `IMicroAgenticaProps.histories` property creating a new `Agentica` instance.
378
378
379
-
By the way, waiting for the completion of internal agents' orchestration and giving prompt results to the user at once is not a good choice in the UX (User Experience) perspective. In that case, it would better to deliver the events to the user step by step with streaming. Enroll event listeners by calling `MicroAgentica.on()` function, and deliver it to the user.
379
+
By the way, waiting for the completion of internal agents' orchestration and giving prompt results to the user at once is not a good choice in the UX (User Experience) perspective. In that case, it would better to deliver the events to the user step by step with streaming. Enroll event listeners by calling `MicroAgentica.on()` function, and deliver it to the user.
You can configure the `throw` property to control error handling behavior.
421
+
422
+
When you set `IMicroAgenticaConfig.throw` to `true`, the agent will throw an exception when function execution fails (`AgenticaExecuteHistory.success === false`). This is useful when you want to handle execution failures explicitly in your application logic.
423
+
424
+
By default, execution failures are handled silently without throwing exceptions. Set this property to `true` if you need to catch and handle execution errors in a try-catch block.
0 commit comments