You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest version of SAT, the idempotency is broken so if we ever re-run the initializer notebook, we re-create all the alerts.
This not only means we end up with lots of old alerts, but also means that any notifications on the alerts we setup manually no longer work.
It looks like a combination of stripping out the preview APIs and moving resources to folders that broke this.
I did take a quick look at fixing this, but it's going to take more time than I thought so I'm not sure if I'll be able to get round to it and we're putting in a workaround for our use-case.
The current alert idempotency code is half commented out, and doesn't work as it uses functionality not present in the API (that I assume was present in the preview API).
If you just fix the alert idempotency code, then the alerts no longer work as each run the folder is deleted. It looks like this deletes the underlying query but not the alert, so by not recreating the alert we end up with a broken alert pointing to a query that no longer exists.
Basically, we'd need to either make sure the queries are not deleted and understand the impact to that, or update the current alerts to use the new query ID.
The text was updated successfully, but these errors were encountered:
With the latest version of SAT, the idempotency is broken so if we ever re-run the initializer notebook, we re-create all the alerts.
This not only means we end up with lots of old alerts, but also means that any notifications on the alerts we setup manually no longer work.
It looks like a combination of stripping out the preview APIs and moving resources to folders that broke this.
I did take a quick look at fixing this, but it's going to take more time than I thought so I'm not sure if I'll be able to get round to it and we're putting in a workaround for our use-case.
The current alert idempotency code is half commented out, and doesn't work as it uses functionality not present in the API (that I assume was present in the preview API).
If you just fix the alert idempotency code, then the alerts no longer work as each run the folder is deleted. It looks like this deletes the underlying query but not the alert, so by not recreating the alert we end up with a broken alert pointing to a query that no longer exists.
Basically, we'd need to either make sure the queries are not deleted and understand the impact to that, or update the current alerts to use the new query ID.
The text was updated successfully, but these errors were encountered: