Wednesday March 6, 2024

Issue summary:

On March 6, 2024 from 7:45 PM PST to around 9:33 PM PST customers reported that they were receiving a 500 error when viewing the legacy Incoming Webhook custom integration page.

We identified a backend code change that inadvertently changed data that the Incoming Webhook page needed to load which consequently caused the page to respond with an HTTP 500 error.

We rolled back the change, correcting the issue and all customers should now be able to access the Incoming Webhook page as expected.

6:35 AM PST

We’ve released a fix and all impacted pages are up and running once again. You may need to reload (Command/Ctrl + Shift + R) any affected pages in your web browser in order for this fix to be reflected on your end. We appreciate your patience while we sorted this out.

9:40 PM PST

Some customers may be experiencing issues accessing the Incoming WebHooks legacy custom integration page. We're aware and investigating the problem.

We apologize for the disruption. We'll provide an update as soon as we have news to share.

7:59 PM PST