Hello team! I'm trying to hunt down a bug that's causing some alerts to fail in one of our workspaces but I need the Snowflake Query ID to really get into the nitty gritty. Any chance someone could grab that for me? Trace ID for the Alert error: 6fbd62c298469997

Hello Sam, I've checked our logs, but from this ID I can see that the message was sent successfully:

"ts": "2025-10-27 13:00:12.795",
  "traceId": "6fbd62c298469997",
  "orgId": "4jx6gagejs",
  "msg": "Message arrived",

Hi Joseph, sorry for the delayed reply. That's strange that it says the message was sent successfully - The alert in the UI is saying that it failed. I double checked the trace ID and it looks right. Here is a screenshot from the Alerts UI showing the error

Hey Sam, Sorry for that... I did find an interception:

Thank you!

Hi Sam, Please allow me to jump in here in the meantime as Joe is currently out of his office hours. I would like to provide some additional information here and maybe ask 1 or 2 questions. 1. Do I understand correctly that neither of the recipients is receiving the Alert - is it failing for both of them? I'm asking because our logs show successful "sent" log but only for

courtney.anderson.princesspolly

2. Was this working before and it started to fail only recently or it never worked in this setup? Is similar/same alert working somewhere else within your environment?

Hi Julius, Apologies for the delay in response: • That is how i understand it, or at least that the alert failed and thus never sent. • I've had a similar alert work for different time frames - I had missed that the alert was set up for all time. 🤦 That's probably part of the issue, let me take this back and see if that alone helps. ◦ Out of curiosity, since the alert is set up for a specific metric value does that not filter the visualization before sending the alert? My understanding of the 'General Error' that the alert was throwing was that there's an issue with the SQL being generated, which is why I had originally asked for the Snowflake Query ID. 🙂

Hi Sam, Thanks for the follow-up. To answer your question: • The alert uses the same dashboard widget (with its full metric logic and filters) that you’ve configured — so the metric is evaluated first, and then the alert condition (e.g., “metric > X”) is applied. This is described in our GoodData documentation (“the active dashboard filters are used by default” when creating an alert). • Because of that, when a visualization becomes non-computable (for example due to “All time” filter or other setup issues) the alert won’t trigger as expected. As my colleague mentioned, it might be worth trying to set the alert for a shorter period than “All time” so we can identify whether this setup is causing the non-computable result you observed. In any case, we are checking this internally with our Technical Support team and will get back to you once we have more information.

Hi Mauricio, I appreciate the support! I've changed the date range to "The Last Two Weeks" for the alert and made sure that the visualization loads with that timeframe. I'll keep an eye on it and see if this resolves the issue. Please keep me updated with what the technical support team finds. Thank you again! 🙂

Hi Sam, Thank you for the update. I just have one last thing to ask: I understand that the visualization is now computing correctly after applying the date filter, but what about the alert? Can you confirm if it is working now? At the moment, I don’t have any updates, but I will share any information I receive with you. Thank you for your patience and help with this.

Hey Mauricio, I haven't received a notification about the alert failing yet, but that's because I don't think it's gone off based on the metric being used for the alert. I'll let you know once I find out if it succeeds or fails once it goes off!

Hi Sam, I have an update, we have been checking internally with out Technical Support team, on our logs and this time we do not see errors. However can you please confirm if the user(s) received the alert on their email?

Hey Mauricio, thanks for checking in! I'm still waiting for the alert to proc again, but I'll let you know as soon as it does! 🙂