Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
customer was unable to locate why notifications were not sent to the topic after a succesful operation. resulted in time of frustration and 3 months of not having notifications
Feature request summary: Customer is running scheduled quureis with notificaiotnss to pubsub
after several moths customer noticed that the notifications were stop flowing to the topic.
customer had hard time understanding why his notifications are not being sent after a SUCCESFULL scheduled query operation.
After my investigations , he was suggested adding the PUBLISHER role to the opreating SA that resolved the issue.
Yet, for now, 3 months that the customer had no notifications sent because someone from his org removed the PUBSUB PUBLISHER role via Terraform code.
Customer would easily see this if there was a PERMISSION DENIED error log emitted after a failure of notification sent .