Hy community , i have created a workflow which uses , nodes like Microsoft outlook trigger and Basic LLM chain node (connected with azure chat model) . after testing the workflow in development phase i have activated it , problem is for any error which occurs at run time like Token limit exceed error in llm node , it halts the execution and for other incoming mails it is not doing any thing and even it is not re executing the same work flow on the same mail . please help me how i can tackle and deal with this run time error problems.
To handle errors in a workflow, you can use the Continue (Using error output) option.
A simple solution might be a Wait node. However, this can quickly lead to many simultaneous executions that never finish, especially when the trigger is rate limits.
For your use case, it would likely be better to save the input parameters (data from email) into a queue and process them with a separate workflow. You could use a database, Google Sheets, or Redis as a simple queue.
Thanks Franz for helping me , but if i can use Continue (Using error output) option. then in this case Basic LLM chain node will not give me any output (means it will not process the text and not give me desired output) it will simply pass on the flow to next node without any halt , also the api key i am using is basically a shared key means multiple projects uses same case so i cannot predict the token limit and set for my Basic LLM chain node ,
Yes, that’s why I suggested using a queue.
Store the received emails in a queue and process them one by one in a separate workflow. Once the limit is reached, pause the workflow and wait until the rate limit lock is removed.
1 Like
The workflow of the Schedule trigger will stop on error of the “No Operation” node (this must be replaced by your workflow) after requeuing the current item.
Or when the get queue item returns no item. - The queue is empty.
1 Like