Forum Discussion
ArchiveUser
7 years agoQrew Captain
I'm getting the same error from Automations, one of which only changes data in the same table (the same record actually).
- EvanMartinez7 years agoModeratorHi Jennifer,
This can happen when you set up an Automation that will trigger itself. For example one that says whenever I edit this record then fire off an Automation that will edit this record. Then when the Automation edits the record it triggers itself again, over and over. Essentially creating a loop. You want to make sure your Automation has some kind of control to prevent this from happening.
A great example of this is if you have an Automation set up so that when a record is edited you then edit the record without any filters. Instead if you have it set so that whenever a record is edited and the Company Name field changes then edit the Company History field the Automation isn't set up to trigger itself. - ArchiveUser7 years agoQrew CaptainYeah, I ran into that in the beginning, but I limited it to only when a record was added, and it's been running for over a week. Just started getting the message about the Webhooks since Tuesday evening.
It's also firing on an Action that only creates a child record when a parent record meeting specific criteria is changed to 100% complete. - EvanMartinez7 years agoModeratorDo you have a number of other Automations that could be firing at the same time within your application from just total traffic? In that instance I would recommend reaching out to the Care team via a support case and see if they can help you isolate when you are hitting that threshold and why. You can create a support case when signed into a Quick Base application by clicking on the question mark icon that appears in the upper right hand corner of Quick Base and selecting Manage Support Cases. You can also create a support case directly here.