Cloudfront API errors after infrastructure change

English Forum Developers & API
1

Hello,

My team has been receiving API 403 errors on and off since January. They have been much more common in the last week so I am finally reaching out. These issues below are similar but they have been marked as resolved.

My response looks like:
Request blocked.
We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n’

This is blocking our team’s webhooks and is a critical issue for us. I would use the deprecated api but it looks like it will be sunsetted soon. Any assistance is created

1 Like
2

As an addendum, I saw some comments suggesting to avoid GET’s with a body. Our failing requests are all POST’s.

3

Me too! I was going crazy thinking it was my fault. In my case, I did discuss with Asana a bit, and it was potentially related to me calling the “get token from refresh token” endpoint too often. In your case it happens with which endpoint?

4

I’ve got it on the /duplicate endpoint and /addTask to section endpoint, among others

5

Hey I’m getting this error as well. Using asana-python package (v5.1.0) deployed in a Cloud Run instance, though it works locally.

\n\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n
\nRequest blocked.\nWe can\'t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n
\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n
\
6

Hi, Thanks for sharing. We are investigating to see what might be causing this.

4 Likes
7

I do notice way more 403 random errors in my logs, and this has been going on for a while…

9

@Gopesh_Kosala I moved your post to another thread on this issue.

@John_Baldo here is someone else having what looks like the same errors.

10

@Gopesh_Kosala, Thank you for bringing this up. I’ve flagged this to our Infra team. They are aware and currently looking into the issue.

11

Thanks @John_Vu and @Phil_Seeman

12

Hi @Gopesh_Kosala, to help our Infra team investigate are you able to provide us with:

  1. Request ID
  2. API URI
  3. Timestamp

Of your most recent issue.

Our Infra team looked up the information about the issue you posted here but that log looks to be a few days old. If you encounter more or any recent ones (i.e., in the last day) please provide us with the above information.

1 Like
13

Hi @John_Vu ,
Here are the details from the recent request,
Request ID: dXZBH5CemD7FARBwhH-EZV3ol39s7bLcZPckHgMsqyoCwZmUcggjBg==

API URI: Same as mentioned in the other post (Unable to post the URI here)

Timestamp: 2025-04-03 1:33 PM IST

14

Hey, I am also experiencing the same issue since February.
Got 403 errors and getting more common as well.

The latest request id : CzCH9XsRNXGKZq0JEHIM9tnvYRCdcxEraYmSvfBQXDOTDUunnHb46w==
Timestamp: 2025-04-01T21:46:00.683939187Z
Endpoint: PUT /tasks

15

Thank you @Gopesh_Kosala and @Dedy_Cds. I’ll pass this info along to our Infra team.

16

Hey there! We’re running into exactly the same issue: on and off 403 errors seemingly related to Cloudfront. We’re calling the Asana API via python in a GCP app engine instance. We’re currently on version 5.0.7 of the asana API.

Is there any indication that this is an error on our end (users of the API)? Or is this an asana-side issue? Is this something that we could handle on our end by building in retry logic when we encounter 403s?

Thanks,
Tom

17

This has been going on for weeks now, I hope it gets resolved soon…