Quickbase action limits ?

The 10 messages per second would be an application wide limitation. It is tied to the number of requests being processed for that application in close proximity. 

In that case, if we have a few chained actions(like, master editing child records and they in turn updating other things), we'll pretty quickly hit the limits and things could fail mid way ? 

I actually just double checked with one of my PD team members for confirmation and they actually let me know that it is 10 per second per table, not just application. Some changes were made to that from its original implementation which is what I was basing my information on. 

Either way though depending on how much traffic you are intending to trigger there is the possibility of running into that limit. 

That's great to know. Would be great if someone could update the documentation that talks about limits in general. Thanks!

Also, these are 10 actions. right ? i.e each action could possibly result in many child records to be updated ? 

That is correct you can have up to 10 actions on a table and each action could possible create many child records depending on your criteria. 

Can you have 10 Webhooks AND 10 Actions? or only 10 total between both? 

I'm like 99% sure it would be 10 in total as I believe under the covers, Actions are just Webhooks for Dummies. (and I will take the Dummy option any time I can!).  I don't know for sure, but I know they are the same thing under the covers, just made user friendly in Actions.

I read somewhere that it's 10 + 10. They are counted differently from what i understood. 

Hmmm, I'm surprised but pleasantly.  I think that Evan will see this in the morning and check this for us officially.

think its 10 and 10...I have a table with 10 webhooks and 6 actions so i'm assuming I can go to 10 actions.

Keith, I was mixing up two things.  I agree that it is 10+10 in terms of the numbers.  But I'm pretty sure that only 10 can fire per second, combined.

not sure about that but you are probably right

I can confirm that currently the limitations for a single table are 10 Actions and 10 Webhooks, you can have up to 10 of each. Mark is also correct that there is also a limit to the number that can fire at once and it is for both Actions and Webhooks combined. The rate limit is 10 Actions or Webhooks firing in 1 second on 1 table. If you go over that you reach the rate threshold and your further Actions/Webhooks are blocked. 

Got it - thanks everyone! 

@BVI.  They are concerned about looping, and infinite loops (not to be confused with Apple's Head Office which is at Infinite Loop drive). 

It is very easy to make an infinite loop, so they have set the limit at a max of 10 per any 1 second period. 

They don't all need to fire at the same time.  For example you could have Actions/ Webhooks in Table A that says to create a record in Table B when a record is created in Table A.  Like a mirror record.  But then you could also have the opposite setup to create a record in Table A when a record in Table B is created.  So those are actually firing sequentially but would fire infinitely and create millions of records pretty quick. So they set that sanity limit of 10 per 1 second elapsed time.