RevOps incident

Background jobs including PDF generation, and Slack and email notifications may be delayed

Minor Resolved View vendor source →

RevOps experienced a minor incident on October 20, 2025 affecting RevOps Console and Salesforce Integration and 1 more component, lasting 3h 8m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:29 PM UTC
Resolved
Oct 21, 2025, 01:38 AM UTC
Duration
3h 8m
Detected by Pingoru
Oct 20, 2025, 10:29 PM UTC

Affected components

RevOps ConsoleSalesforce IntegrationHubSpot Integration

Update timeline

  1. investigating Oct 20, 2025, 10:29 PM UTC

    Service degradation issues for this morning seems to have re-appeared. We are currently investigating any impact to RevOps CPQ customers and taking steps to resolve the issues.

  2. monitoring Oct 20, 2025, 11:15 PM UTC

    A change in our platform appears to be the root cause of the service degradation. We have rolled back the change and we are seeing a reduction in error rates. We will continue to monitor and update any impacted deals or other platform resources.

  3. monitoring Oct 20, 2025, 11:49 PM UTC

    PDF Generation and all other background jobs have stabilized and are performing with no issues now. We are also aware of issues with Slack and email notifications not being received, this is related to incidents from upstream providers. While Slack notification error rates are decreasing, email notification error rates are no long increasing. We will continue to monitor these services. We are beginning investigation of impacted deals and failed notifications, and will update deals and resend notifications. If you are missing expected notifications, you will begin to receive them shortly.

  4. resolved Oct 21, 2025, 01:38 AM UTC

    Impacted deals and failed notifications have been updated and resend, respectively. All upstream providers are reporting resolved incidents and all of our previously degraded services are now completely restored. If you have any questions or comments, or think you're still impacted, please reach out to us at [email protected]