AppFlow (HubSpot) to S3 Integration Suddenly Failing with 400 (Bad Request) Error

Developer Support APIs & Integrations
1

Hi everyone,

I’ve had an AppFlow integration running from HubSpot to S3 for almost six months without any issues. However, starting this past Friday, I’m getting the following error:

“The request failed because the service Source HubSpot returned the following error: Details: The request failed with status code 400 (Bad Request). There was a problem with the request. Status code 400 (Bad Request). ErrorCode: ClientError.”

Usually, the flow processes around 500 records, but from the point of failure, it seems there are about 9,000 records being processed. There haven’t been any changes to the field mappings, and we’re using HubSpot’s v3 API.

I’ve been unable to debug the issue. Has anyone encountered a similar problem or have suggestions on how to resolve this? Any help would be greatly appreciated!

2

Hey, @AMaxwel Thanks for your question. I have a few questions to help give our community more details.

  • Do you know what caused the increase in records to process?

Troubleshooting:

  • Have you tried breaking the batch into smaller requests? To see if it will process using a smaller number of a records
  • Have you tried using Postman, or a similar tool, to simulate the request manually with a smaller dataset. To try to isolate if the error is related to the data or to the volume
  • Have you examined your auth token to see if there is a rate limit error showing up on the HubSpot side of things? Legacy public apps - HubSpot docs

Thanks for the additional information! — Jaycee