New Relic – Dashboard Creation Issues – US and EU region

by

Dec 10, 11:17 UTC
Resolved – Between 10:20 UTC and 11:00 UTC on December 10th, some customers in the US and EU regions may have experienced issues creating new dashboards.

We have investigated and resolved this service interruption and impacted services have returned to normal operations.

Dec 10, 10:57 UTC
Update – We are investigating an issue that may impact the creation of new dashboards for customer accounts in the US and EU regions

Dec 10, 10:53 UTC
Update – We are continuing to investigate this issue.

Dec 10, 10:50 UTC
Investigating – We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

Bubble – Issues with Main Bubble Cluster

by

Dec 9, 15:00 EST
Resolved – Our systems are functional and we are closing out this incident.

Dec 9, 14:38 EST
Investigating – We are investigating reports of issues with our systems.

Bubble – Issues with Main Bubble Cluster

by

Dec 9, 14:30 EST
Resolved – Our systems are functional and we are closing out this incident.

Dec 9, 13:49 EST
Investigating – We are investigating reports of issues with our systems.

Zapier – Error on Sub-Zap Runs

by

Dec 9, 07:43 PST
Resolved – Between 10:57 AM UTC and 2:00 PM UTC, customers experienced failures when triggering Sub-Zaps, accompanied by the error message: “The app returned ‘You do not have permission to perform this action.'”

The underlying issue was identified and corrected by 2:00 PM UTC. All affected Zap runs have been successfully replayed, ensuring workflows are restored without customer intervention. Thank you for your patience as our team worked to resolve this.

If you have additional questions, please contact our support team at https://zapier.com/app/get-help.

Dec 9, 04:18 PST
Identified – Customers are experiencing failures with their Zaps when triggering sub-Zaps. The error message displayed is:
“The app returned ‘You do not have permission to perform this action.’”

This issue occurs even when customers own both the main Zap and the sub-Zap, suggesting the error is not related to actual permission settings. It is affecting multiple Zaps and disrupting workflows. Investigation into the root cause is ongoing.