OnceHub incident

We are aware of an intermittent issue causing some Zaps to trigger excessively

Minor Resolved View vendor source →

OnceHub experienced a minor incident on July 22, 2025 affecting Third Party Integrations, lasting 2h 50m. The incident has been resolved; the full update timeline is below.

Started
Jul 22, 2025, 11:20 AM UTC
Resolved
Jul 22, 2025, 02:10 PM UTC
Duration
2h 50m
Detected by Pingoru
Jul 22, 2025, 11:20 AM UTC

Affected components

Third Party Integrations

Update timeline

  1. investigating Jul 22, 2025, 11:20 AM UTC

    ISSUE DETECTED: We are aware of an intermittent issue causing some Zaps to trigger excessively. We are actively working with Zapier to identify and resolve the problem. We will provide updates as soon as possible.

  2. monitoring Jul 22, 2025, 12:24 PM UTC

    INCIDENT UPDATE: We're investigating an issue causing some Zaps to trigger excessively. As a potential workaround, disabling Two-way sync may resolve the issue in some cases. While this may help solve the problem, if it doesn’t or you don’t see the option, please reach out to us at [email protected].

  3. monitoring Jul 22, 2025, 01:05 PM UTC

    INCIDENT UPDATE: Our developers have identified the root cause of the issue causing Zaps to be triggered multiple times and are working on deploying a fix. We will post further updates here as they become available.

  4. resolved Jul 22, 2025, 02:10 PM UTC

    INCIDENT RESOLVED: The issue causing Zaps to be triggered multiple times has been resolved. If you continue to experience any issues, please contact our support team at [email protected].