Unable to load collection item details

For some reason, I cannot access the details for one of our collections. We currently have five remote environments, where two of them are completely accessible, and the other three cannot open the details page.

All environments run the same branch, and nothing has changed in our deployment process.
Example from the environment ID 53361


Request URL: https://forestadmin-us1.tymeshift.io/forest/accounts/77733?timezone=Europe%2FLisbon
Request Method: GET
Status Code: 502 
Referrer Policy: origin

Request headers

:authority: forestadmin-us1.tymeshift.io
:method: GET
:path: /forest/accounts/77733?timezone=Europe%2FLisbon
:scheme: https
accept: application/json
accept-encoding: gzip, deflate, br
accept-language: en-GB,en;q=0.9,pt-BR;q=0.8,pt;q=0.7,en-US;q=0.6
authorization: [...]
cache-control: no-cache
content-type: application/json
dnt: 1
forest-context-url: https://app.forestadmin.com/TymeshiftFA/us1/Tymeshift%20Default%20Team/data/accounts/index
origin: https://app.forestadmin.com
pragma: no-cache
referer: https://app.forestadmin.com/
sec-ch-ua: "Not_A Brand";v="99", "Microsoft Edge";v="109", "Chromium";v="109"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "macOS"
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: cross-site
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36 Edg/109.0.1518.78


Feature(s) impacted

Cannot access the collection item details

Observed behavior

HTTP 502 and app crash

Expected behavior

Load the collection item details page

Failure Logs


  • Project name: TymeshiftFA
  • Environment name: US1, US2, EU1
  • Recent changes made on your end if any: none

It got solved w/o any intervention from our side.
Can you check what produced this behavior on your side, please? :thinking:

Thank for your report I will check on our side what happened.

Appreciate, @Alban_Bertolini :pray:
It has been happening since 10am GMT – this part of the app was completely off for almost 4 hours, impacting our sales team.

it could be your agent who had a problem.
Do you have some logs on your agent ?
I just looked at our logs on our side and there is nothing alarming.

I will check for the logs.
Is there something to be done on our side when facing issues like that? Do you have a guideline to troubleshoot these scenarios?

Sorry we don’t have guide to help our customer.

Did you find any logs ?