Hi,
I have a scenario in which Make updates a record. Every time I get a response that the scenario is timed out (+ 45 seconds)… Anyone is experiencing similar issues? I need to update the record, since if not an automation rule will continue to be processed every time a record is edited.
Regards Martijn
This happens to me from time to time, I just added a Break module to the Scenario to handle the timeouts.
@SuiteUpstairs , thanks but I doubt that is going to help, since the 45 seconds is taking Make solely to update a record, based on a record Id from 2 steps before. Maybe I can update the record with the catch TB function, but I have to figure out first how to send a webhook from make to TB. I only know make as the receiving part namely and not as the sending part of the webhooks. From my current knowledge I have to use the https module and then send a request to catch tabase.
If you add a break to the Tadabase module, it will kick in if the Tadabase server times-out, then it will try to update the record again after the set Interval time and it will retry as many times as you set the “Number of Attempts”. It shouldn’t take more than a second for a record to update so if it is taking 45 seconds, it most likely means the Tadabase server is not reachable in which case adding this will help.
You can use the “Call an API” module on Make, then add the following to the headers:
X-Tadabase-Queue-Equation: 1
This will create a job for the equation to run in the background.
Reference: Tadabase API
thanks for the suggestion, your solution works. however, due to speed necessity I implemented the catch TB webhook. It goes really fast.
