Workato Tip of the Day: Avoid XML Pitfalls with Reserved Keywords!Did you know? In Workato, using <command> in an XML message template might show a red mark at the bottom. This happens because command may be reserved keyword in Workato. ( image a...
Hi Team,I came across a small correction needed in the Workato docs:If we observe carefully, the template used an object instead of an array.Please use an array when you want to retrieve multiple values in the template response.
Hi Team,I've noticed a minor discrepancy: there are two different default polling interval times present in two separate workspaces.Fig1. shows default value as 30mins Fig.2 shows default value as 5mins Could you please make necessary correction?
Hi @gsRatti1 and @Prudvi,After reviewing the comments, I found that OAuth 2.0 supports real-time triggers.I've attached a screenshot for your reference. Please use an API Token for the authorization process.Please let me know if you need further help...
Hi @rlaib ,Yes, `refresh_on` applies only to authentication-related errors, not all cases. If you believe certain error codes specifically indicate an authorization issue that requires a token refresh, it's best to explicitly specify those error code...
Hi @rlaib,Here are my thoughts on my understanding retry_on_* and refresh_onWorkato prioritizes refresh_on before retry_on_* when handling authentication-related errors. If an API request fails with an authentication error (like 401 Unauthorized or 4...
@Prudvi ,Trigger is a starting point of our recipe.Error Handling cannot be implemented directly inside a Trigger step in Workato. Triggers are responsible for detecting events and initiating recipes, but they do not support Monitor or Error blocks w...
Hi @Prudvi,Error handling should be customized based on the use case, as different scenarios require different approaches to notifications and resolution strategies. Relying entirely on Workato’s default handling could lead to a lack of differentiati...
