SMB Trigger - Recipe stopped due to 60 consecutive trigger failures

[gnaneswar]

I’m facing an issue with the SMB connector when used as a trigger in my recipe.

The recipe stops automatically with the error message:

“Your recipe has been stopped because of 60 consecutive trigger failures.”

When I use a Scheduler trigger instead of SMB, the recipe runs smoothly without any issues.

Could anyone please help me understand why this error occurs when using SMB as a trigger?
Also, is there any recommended way to avoid consecutive trigger failures or improve the stability when using SMB triggers?

Thank you in advance for your help!

[girish-naralla]

Hi @gnaneswar ,

In Workato, the concept of Trigger Error Threshold refers to the platform's automatic safeguard mechanism that stops a recipe after it encounters 60 consecutive trigger errors, indicating a persistent issue rather than a temporary glitch.
In your case, since you're using an SMB connector via an On-Prem Agent (OPA), the recipe depends on the agent to fetch data from on-premise systems like file servers. If the OPA consistently fails to connect or retrieve data due to reasons such as an inactive service, network access issues, expired credentials, misconfigurations, or system resource overload. Workato logs these as trigger errors. Once the threshold is reached, the recipe is halted to prevent further failures.

To troubleshoot, you should check the OPA logs, restart the agent, validate connection profiles, manually test the trigger, and leverage RecipeOps for proactive monitoring and alerting.

If the issue persists, a more reliable alternative would be to use a scheduler based recipe that checks for new files at regular intervals, reducing dependency on real-time triggers.

Thanks, 
Girish Kumar Naralla