Status code was not 200. Returned status code:500

[jdeverdun]

Hello everyone,

Since a few day I've got the error (on any request):
Error in interest_over_time(widget, comparison_item, tz) :
Status code was not 200. Returned status code:500

I first though it was a daily limit, yet I still havethis issue on other computer. Am I the only one ?

EDIT : the issue seems to be related to the time range, it fails when I give for example
a=gtrends( 'bike' , geo = 'FR' ,time= 'now 1-d' , low_search_volume = TRUE)

but it "does not fail" when date range is specified.

I guess it is related to google trends itself, but wanted to make sure !

Thanks for your help.

Best regards

[lukschue]

Hello jdeverdun,

You are not the only one. I gather Google Trends data automatically on a daily basis for a project and since today I got the same Error code for all my request. Though until yesterday it still seemed to work out for me.

And also when the range is specified it does still work.

I hope this problem is solvable.

Kind regards.

[PMassicotte]

I am also getting the error, but only for the "past day" search. I will investigate this.

[jdeverdun]

Just to let you know I tried various tools, like pytrends and even serpAPI but same, I guess google is doing some work

[shrikant2002]

same happening with me since 3 days

[ccharisis]

Same issue for me. Started yesterday.

[ccharisis]

I am also getting the error, but only for the "past day" search. I will investigate this.

Hi! Do you have any update on the issue? I am still getting the same error when I use "now" time formats like "now 1-H" or "now 1-d" etc. The other time formats like 'today 1-m' seem to work fine. So it looks like an issue that affects only the "Last" n hours /days and not the "Past" queries. Please let me know if you have any updates on the problem.

[xritzim]

Hello, I'm experiencing the same issue. I get the status code 500.

[PMassicotte]

This is what we are sending:

{
  "userConfig": {
    "userType": "USER_TYPE_SCRAPER"
  },
  "locale": "en-US",
  "comparisonItem": [
    {
      "geo": {
        "country": "FR"
      },
      "complexKeywordsRestriction": {
        "keyword": [
          {
            "type": "BROAD",
            "value": "bike"
          }
        ]
      }
    }
  ],
  "resolution": "EIGHT_MINUTE",
  "requestOptions": {
    "category": 0,
    "backend": "CM",
    "property": ""
  },
  "time": "2023-07-04T12\\:03\\:43 2023-07-05T12\\:03\\:43"
}

This is what Google Trends (website) is sending:

{
  "time": "2023-07-04T11\\:36\\:47 2023-07-05T11\\:36\\:47",
  "resolution": "EIGHT_MINUTE",
  "locale": "en-US",
  "comparisonItem": [
    {
      "geo": {
        "country": "FR"
      },
      "complexKeywordsRestriction": {
        "keyword": [
          {
            "type": "BROAD",
            "value": "bike"
          }
        ]
      }
    }
  ],
  "requestOptions": {
    "property": "",
    "backend": "CM",
    "category": 0
  },
  "userConfig": {
    "userType": "USER_TYPE_LEGIT_USER"
  }
}

Besides userType, this is the same. So I do not know what is going on at the moment. Note that userType is also set to USER_TYPE_SCRAPER when we use other time ranges such as date=today 5-y so this is not obvious that this is the cause of the problem.

[jdeverdun]

Thanks for this information, I also checked on the google trends website and in fact we can see that if you try to access the embed code for the interest by city map, we also have a 505 error for this kind of request (still working fine for specific date request).

So again, google should be working on it.

Best

[PMassicotte]

I will keep an eye open for this.

[ccharisis]

I will keep an eye open for this.

Thank you.

[Helldez]

Hi, does anyone have any updates on this? It seems to be a Google Trends issue, but does anyone know if it's transient or we need to find another way to fetch the weekly and daily data?