Unable to access my data: The request to your server failed or returned invalid data

Help me!
1

When I try to access some data like Sneakers, Sneaker Photos or Events, the loading time is very long

Capture d’écran 2022-03-22 à 14.57.20
Capture d’écran 2022-03-22 à 14.57.203360×1944 381 KB

Once the loading is complete, it is impossible for us to access some data with the message “The request to your server either failed or returned invalid data. Please check your console logs to get more information.”

Capture d’écran 2022-03-22 à 15.01.53
Capture d’écran 2022-03-22 à 15.01.533360×1940 202 KB

Feature(s) impacted

Some data are not accessible

Observed behavior

The requests are not successful

Expected behavior

Regain access to data that is no longer accessible

Failure Logs

2022-03-22T13:44:44.153170+00:00 app[web.1]: OPTIONS /forest/Sneakers?timezone=Europe%2FParis&fields%5BSneakers%5D=pictureURL%2Cname%2Cbrand%2Cmodel%2CbackgroundColor%2CsliderBackgroundColor%2CreleaseDate%2CreleaseDateType%2Ccode%2Ccolorway%2CresellEstimation%2CresellPrice%2Ccollaboration%2CcollaborationBrandOne%2CcollaborationBrandTwo%2Cpack%2CcopCount%2CdropCount%2Conly%2CpriceDetail%2CpriceResellTBA%2Cstar%2CstarUI%2CrestockDate%2CrestockDateType%2CpictureData%2CsliderIconColor%2Chidden%2CcreatedAt%2CupdatedAt&fields%5Bbrand%5D=name&fields%5Bmodel%5D=name&page%5Bnumber%5D=1&page%5Bsize%5D=150&sort=-releaseDate 204 0.261 ms - 0
2022-03-22T13:44:44.301670+00:00 app[web.1]: OPTIONS /forest/Sneakers/count?fields%5BSneakers%5D=pictureURL%2Cname%2Cbrand%2Cmodel%2CbackgroundColor%2CsliderBackgroundColor%2CreleaseDate%2CreleaseDateType%2Ccode%2Ccolorway%2CresellEstimation%2CresellPrice%2Ccollaboration%2CcollaborationBrandOne%2CcollaborationBrandTwo%2Cpack%2CcopCount%2CdropCount%2Conly%2CpriceDetail%2CpriceResellTBA%2Cstar%2CstarUI%2CrestockDate%2CrestockDateType%2CpictureData%2CsliderIconColor%2Chidden%2CcreatedAt%2CupdatedAt&fields%5Bbrand%5D=name&fields%5Bmodel%5D=name&timezone=Europe%2FParis 204 0.203 ms - 0
2022-03-22T13:44:44.419808+00:00 heroku[router]: at=info method=GET path="/forest/Sneakers/count?fields%5BSneakers%5D=pictureURL%2Cname%2Cbrand%2Cmodel%2CbackgroundColor%2CsliderBackgroundColor%2CreleaseDate%2CreleaseDateType%2Ccode%2Ccolorway%2CresellEstimation%2CresellPrice%2Ccollaboration%2CcollaborationBrandOne%2CcollaborationBrandTwo%2Cpack%2CcopCount%2CdropCount%2Conly%2CpriceDetail%2CpriceResellTBA%2Cstar%2CstarUI%2CrestockDate%2CrestockDateType%2CpictureData%2CsliderIconColor%2Chidden%2CcreatedAt%2CupdatedAt&fields%5Bbrand%5D=name&fields%5Bmodel%5D=name&timezone=Europe%2FParis" host=yonkt.herokuapp.com request_id=722f8a37-622d-4ead-b0c5-ed857302f939 fwd="176.176.217.161" dyno=web.1 connect=0ms service=36ms status=304 bytes=261 protocol=https
2022-03-22T13:45:00.896837+00:00 heroku[router]: at=info method=GET path="/public/email/yonkt-mail-background.png" host=yonkt.herokuapp.com request_id=deaf76eb-34c3-4e26-bdf5-51fcfe2d5431 fwd="66.249.92.62" dyno=web.1 connect=0ms service=11ms status=200 bytes=804880 protocol=https
2022-03-22T13:45:14.199347+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/forest/Sneakers?timezone=Europe%2FParis&fields%5BSneakers%5D=pictureURL%2Cname%2Cbrand%2Cmodel%2CbackgroundColor%2CsliderBackgroundColor%2CreleaseDate%2CreleaseDateType%2Ccode%2Ccolorway%2CresellEstimation%2CresellPrice%2Ccollaboration%2CcollaborationBrandOne%2CcollaborationBrandTwo%2Cpack%2CcopCount%2CdropCount%2Conly%2CpriceDetail%2CpriceResellTBA%2Cstar%2CstarUI%2CrestockDate%2CrestockDateType%2CpictureData%2CsliderIconColor%2Chidden%2CcreatedAt%2CupdatedAt&fields%5Bbrand%5D=name&fields%5Bmodel%5D=name&page%5Bnumber%5D=1&page%5Bsize%5D=150&sort=-releaseDate" host=yonkt.herokuapp.com request_id=3d94de7c-c9e9-4fa9-ae28-4268f283918d fwd="176.176.217.161" dyno=web.1 connect=0ms service=30008ms status=503 bytes=0 protocol=https
2022-03-22T13:45:14.200859+00:00 app[web.1]: GET /forest/Sneakers?timezone=Europe%2FParis&fields%5BSneakers%5D=pictureURL%2Cname%2Cbrand%2Cmodel%2CbackgroundColor%2CsliderBackgroundColor%2CreleaseDate%2CreleaseDateType%2Ccode%2Ccolorway%2CresellEstimation%2CresellPrice%2Ccollaboration%2CcollaborationBrandOne%2CcollaborationBrandTwo%2Cpack%2CcopCount%2CdropCount%2Conly%2CpriceDetail%2CpriceResellTBA%2Cstar%2CstarUI%2CrestockDate%2CrestockDateType%2CpictureData%2CsliderIconColor%2Chidden%2CcreatedAt%2CupdatedAt&fields%5Bbrand%5D=name&fields%5Bmodel%5D=name&page%5Bnumber%5D=1&page%5Bsize%5D=150&sort=-releaseDate - - ms - -

Context

  • Project name: Yonkt
  • Team name: Operations
  • Environment name: Production
  • Agent type & version: “forest-express”: “^8.7.1",
    “forest-express-mongoose”: “^7.8.1",
2

Hello @Yonkt ! :wave: Welcome to our community :tada: :confetti_ball:

Ok, it seems to be a timeout issue.

Let try to find what cause the issue.

  • Did you define Smart Fields or Smart Relationship in the Sneakers collection ?
  • Did you override the GET /forest/Sneakers route ?

Kind regards,
Morgan

3

Hello ! Thank you for your quick response.

No, we have not override the GET /forest/Sneakers route

Yes we have smart fields but we haven’t modified them for a while.

We haven’t modified the server for at least 3/4 weeks

4

Thanks for your answers.

The issue comes directly from Heroku, either because your infrastructure (database/processing) is taking too long to respond (over charged) or because you are trying to load too many heavy resources.

  • Can you check that your heroku database is running correctly ?

You can also try to decrease the number of record shown per page. Than investigate to see if something is causing long request time.

Here are some relevant article from Heroku.

Kind regards,
Morgan