Fivetran incident
3rd Party: Awin connection syncs are failing with 500 internal server error for transaction endpoint
Fivetran experienced a minor incident on April 4, 2026 affecting Awin, lasting 5h 5m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 04, 2026, 08:05 AM UTC
The issue has been identified as originating from the source side and we are working to resolve it.
- identified Apr 04, 2026, 08:44 AM UTC
As a temporary workaround, our development team is skipping the Transaction endpoint. We will contact the source to investigate the issue and work on a fix.
- monitoring Apr 04, 2026, 10:52 AM UTC
We have successfully implemented a workaround by skipping the Transaction endpoint sync for now. We will continue monitoring all affected connections and have also reached out to the awin source team.
- resolved Apr 04, 2026, 01:10 PM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for Awin connections which resulted in syncs failing with a 500 internal server error for Transaction endpoint. Timeline: This issue began on 2026-04-04 at 06:40 AM UTC and was resolved on 2026-04-04 at 10:00 AM UTC. Cause: This was determined to be a source-side issue. Resolution: We’ve implemented a workaround by skipping the Transaction endpoint sync, and the connections are now syncing successfully. We’ve also reached out to Awin Support for more details on these failures. Once the issue on the source side is resolved, the Transaction table will automatically resume syncing data. Additionally, the Transaction table runs a weekly override re-sync, so any skipped data will be backfilled during that process.