If a Netsuite connector is initialized and the attached Netsuite role is subsequently updated with a new or updated permission, I've noticed that the connector isn't made aware of this change either immediately or after a few minutes.I couldn't find ...
When an SDK action fails (e.g. non-200 response code), it's unclear how to access the JSON body of the response to then turn this into a meaningful error message. The "Error Message" pill available through the On Error block does not contain enough i...
I believe I've uncovered a rather serious bug. Let's say I have a repeat action and if an error occurs during an iteration, I want to catch it, wait X seconds, then retry the whole repeat action again. Simple Ruby program that demonstrates this:Outp...
We have error handling retry logic that re-runs our recipe up to some max_attempts whenever we hit API rate limits. Since our recipe creates a Collection as part of its logic, we started seeing failures due to "table name already exists" -- which I s...
Hi, is there a simple way to build in exponential backoff when hit with a rate limit API error? The error handling step allows for retries, but there doesn't seem to be a way to set custom wait intervals in between tries. Perhaps something that can b...
Hi Amy, yes that works in this example! Thank you for sharing that. However, there may be cases where we may still need the list to be scoped within the context of the outer loop. Regardless of the use case though, it seems that the way Workato manag...
Right, so I guess my question is why is it maintaining an offset? It should be recreating the list and the repeat helper list each time a new retry is executed. Ideally, this means the index is always reset to 0. If you refresh the recipe I shared, y...
Hi, thanks for the reply! There are 2 loops here. The outer loop is what controls the re-attempts and the inner loop is what's causing the issue. The entire inner loop is wrapped in a monitor block, which means it should be repeating in full each tim...
