I have a Zap with a Quickbooks “New Invoice” Trigger that is not working reliably.
Sometimes the Zap will trigger instantly, other times it will take multiple hours to trigger, other times it won’t trigger at all. There are never any errored Zaps, it either works or it doesn’t show up in the Zap history at all.
Because of this it is my suspicion that something is going wrong on Quickbooks end, so there isn’t much I can do to troubleshoot.
The Trigger is supposed to always be an Instant Trigger, so it seems like the quickbooks API is simply not sending some of the New Invoice Events.
The Zap is sending invoice information to our Airtable for Order Processing purposes, so if an invoice doesn’t get sent via the zap it can cause an order to go missing. So it’s pretty important for this Zap to work reliably.
Has anyone else experienced this and is there anything I can do to mitigate it?
Best answer by SamBBest answer by SamB
Hi folks! 👋
As Ken mentioned the incident has now been resolved, and the bug report has been closed. If you missed the latest update on the status page or the email notification that was sent, here’s the key details from that update:
We’ve confirmed that the fix implemented by the QuickBooks team on April 8 successfully resolved the issue. There was a period of catch up for hooks that were delayed. The backlog of events that had accumulated prior to the fix has now been cleared, and Zap activity should be operating as expected.
As the issue has been marked as resolved we’ll be closing out this thread.
@CA1, @inmotion (and anyone else that may still experiencing delays), I’d recommend reaching out to our Support team directly about this. They can investigate further on their end to help determine whether the issue has resurfaced and what can be done to get things back on track.
Quick update on my side I just tried to use directly the QBO API and it works like a charm so issue is really between zapier and QBO not QBO themselves. I know QBO are often changing their API so I feel this issue has something to do with that.
Thanks for letting us know, @MR_Concept. Just to clarify, are you receiving webhook notifications directly from QuickBooks without any delays or are you using a GET request to obtain the information from QuickBooks?
@Turbulences and @AWSB, sorry you’re being affected by this as well. I’ve added you both to the list as well so you’ll be notified as soon as it’s sorted and I’ll follow up with an update here shortly.
That incident page will be the best place to go for the most up to date status of the issue. So I’d recommend subscribing to updates on that page to get an instant notification via SMS and/or email as soon as a new update is posted on the incident report page:
Thanks again for everyone’s continued patience on this, it’s much appreciated! 🧡
@SamB I am receiving webhooks without any delay. I am not requesting anything from qbo simply when I create a new invoice, I get the webhook directly in my application
I’m not sure this issue is completely solved. I noticed zaps coming over quickly this weekend, but now we’re getting delays of an hour or more and some Estimates that we’ve created this morning in QB have not triggered a zap at all.
It was working fine last week after we received the update stating the issue was resolved. Today we are also noticing large delays and inconsistencies with the Zaps being triggered.
Admin, please make sure that a new ticket is opened if the last one was closed.
It looks like QuickBooks Online has deployed a fix and hooks have now come in again. Could you please confirm if the issue has been fixed on your end?
Can you please confirm that the Zapier team knows this issue is not fixed. We’re having issues again with Zaps not being triggered in a timely manner (or at all).
As Ken mentioned the incident has now been resolved, and the bug report has been closed. If you missed the latest update on the status page or the email notification that was sent, here’s the key details from that update:
We’ve confirmed that the fix implemented by the QuickBooks team on April 8 successfully resolved the issue. There was a period of catch up for hooks that were delayed. The backlog of events that had accumulated prior to the fix has now been cleared, and Zap activity should be operating as expected.
As the issue has been marked as resolved we’ll be closing out this thread.
@CA1, @inmotion (and anyone else that may still experiencing delays), I’d recommend reaching out to our Support team directly about this. They can investigate further on their end to help determine whether the issue has resurfaced and what can be done to get things back on track.
