Feature Request: Native Fallback Mechanism for Integration & Action Block Timeouts

There’s a workaround for that, which is checking that the required fields that you’ll be populating have any values after the integration. If they don’t, you can safely assume it failed.

Having this feature that you mention though would save a bunch of time!

Thank you for your reply. Do you have an example flow for this workaround? The support team mentioned they are currently testing a workaround using Rules, which might be the same method you mentioned.

Does the Condition block (I’m assuming the checks are done using a Condition block) come after the action? If so, I’m a bit confused about the logic. Wouldn’t the flow terminate before the condition is even triggered?

​@Desmond like this:

;)

Thank you ​@Gustavo Boregio for taking the time to create this example flow! However, I don’t think it would work for my scenario, as I am using the "Insert Row" action, which does not allow assigning values to a User Field within the same step.

Also, the issue I'm encountering is that if the Insert Row request times out or fails, the entire flow stops before the first message is sent, so the above workaround might not work.

Additionally, we've also faced problems in the past with "Update" or "Get" requests to Google Sheets that often takes longer to process than "Insert", which led to constant quota limits being exceeded in the error logs.

Got it!

In these cases I’ve resorted to Make.com to get more control…

It’s not ideal, but it does give me more flexibility to control the automation.

Also, I’ve used the Google Sheet action in a separate (parallel) automation.

For example, have it triggered by a rule that lives outside the main automation, and trigger the rule from the main automation (for example by tagging the person). This way, if the rule fails, the automation still runs smoothly since they’re running in parallel. ;)

Hope this helps!