I've been looking but haven't found any documentat...
# gooddata-cloud
i
I've been looking but haven't found any documentation on
DAILY_ALERT_ACTION_COUNT
- is there documentation someone could point me to for more details on Scheduled Email/Alert limits? For context, I found this thread and I'm looking for more details on this.
j
Hi Ian, Let me double-check this for you.
i
Awesome, thanks!
@Julius Kos any luck finding some information on that? Thanks in advance 🙂
Looking to get a follow up on this if possible - thanks in advance!
m
Hi Ian, here Mauricio from GoodData Support. Currently we are waiting more details about the Daily Alert from our Production team. Once we have an update I will let you know. Thank you for your patience 🙂
🙌 1
i
Thanks - looking forward to information you have on this.
Any chance at a follow up on this one?
m
Hi Ian, once more thank you for your question, and now a valuable feedback, we asked internally and discussed with the specific Team in charge of the 'issue' and missing documentation. They are currently working on the public documentation about these limits. I will keep you posted once the Documentation is available. Finally, regarding the explanation of
DAILY_ALERT_ACTION_COUNT
it is the same you can see in the mentioned thread on your main message. Thank you for your patience.
i
Thank you Mauricio! Is there a way using the API maybe to find out what the explicit action limit is? In the original thread I linked there's a brief mention of the exceeding of "360 actions" however it's not clear if this is a hard limit or where that number comes from.
m
Hello Ian, Unfortunately these limit are Hard Limits. As Workaround you could reduce the frequency, besides hourly and if it works for you, you could try each 4hrs, and then you would be able to include more users in the alert.
i
What is the hard limit? Exactly how many actions does an Org get per day?
m
Hi Ian, the
DAILY_ALERT_ACTION_COUNT
is the hard limit, and comes from our engineers/implementation. It is a feature still is in the first phase thus we are performing analysis about the impact in our hardware and it is planned an increase of the limit. Regarding the definition, is the amount of executions of alerts per workspace you can do in 24 hours, to get the real number you need to consider AutomationCount, but also evaluation frequency and amount of recipients. For example, having 5 recipients in 4 automations with hourly evaluation produces 5*4*24 = 480 actions. Therefore, if the Evaluation frequency is defined Hourly, then the Action Count will depend on the number of Recipients and the number of Automations. And once more, the limit is per workspace, no per Org.
i
So is this a value I can set per workspace? Can I just set
DAILY_ALERT_ACTION_COUNT
to 2000 or something like that? What I'm looking for is the exact number of actions per workspace allowed per day. Is it unlimited? Is it 480? or is it a value I can set?
m
My apologies I thought I mentioned, the limit is 360 actions. And it can not be changed.
i
Okay thank you, that's what I was looking to find out. Looking forward to the documentation release. Is there a way I can be notified when it comes out?
✅ 1
m
Your welcome, I am sorry for the misunderstanding. I will keep our internal ticket in Hold. And once we have the documentation online I will notify you.
🙌 1
i
No worries Mauricio - I appreciate all the details you've provided - they've already been really useful thank you for following up! You all are a fantastic resource whenever I'm stumped 😄