Fivetran incident
3rd Party: QuickBooks connections failing with “Failed to sync 1 endpoint” error
Fivetran experienced a minor incident on July 7, 2026 affecting QuickBooks, lasting 2h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 07, 2026, 05:20 PM UTC
The issue has been identified and we are working to resolve it.
- identified Jul 07, 2026, 05:40 PM UTC
We have identified that the issue occurs when querying the CreditCardPaymentTxn entity. The source API is returning the following error: "invalid context declaration: creditcardpaymenttxn" This appears to be happening because the source may have changed the entity name from CreditCardPaymentTxn to CreditCardPayment. Our team is working on accommodating this change. Next Expected Update: 1 hour
- monitoring Jul 07, 2026, 07:07 PM UTC
We have deployed a fix for this issue by switching to the new entity for data retrieval for the table CreditCardPayment We will continue to closely monitor all affected connections until they have fully recovered and returned to normal sync operations. Next Expected Update: 1 Hour
- resolved Jul 07, 2026, 08:09 PM UTC
This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. Incident Summary Description: We identified an issue affecting QuickBooks connections that caused syncs to fail for the CreditCardPaymentTxn entity. Timeline: The issue began on 2026-07-07 at 2:00 PM UTC and was resolved on 2026-07-07 at 7:10 PM UTC. Cause: The QuickBooks query entity was changed from CreditCardPaymentTxn to CreditCardPayment, causing API requests made by the connector to fail with a 400 ValidationFault. Resolution: We made the required changes for the connector to use the new CreditCardPayment query entity. After deploying this change, the affected connectors recovered successfully, and syncs resumed normal operation.