Recent Upgrade to Forest Admin Pro, 409 in production

Help me!
1

Feature(s) impacted

We upgraded to Forest Admin Pro today, all the collections in production return a 409 error, everything still works in development.
We have been using forest admin in free tier for 2 years prior to this without any problems, then tried the pro trial and everything was fine.

Observed behavior

When trying to access any collection I get the message HttpError: HTTP Error 409: conflict in the console, and nothing is displayed except an error screen.

Expected behavior

No error and all collections should be accessible.

Context

  • Project name: Sumo Backend
  • Team name: Operations
  • Environment name: Staging (production in the usage)
  • Agent technology: rails
  • Agent (forest package) name & version: forest_liana 9.7.0
  • Database type: postgres
  • Recent changes made on your end if any: Upgraded to Pro After using free version for 2 years, upgraded the versions of forest_liana from 8.0.12 to 9.7.0 reading another thread describing the same problem → the problem is still there in version 9.7.0.
2

Hey :wave: And welcome to our community!

According to our internal backoffice, you recently installed our latest version of the agent, did it fix your issue?

If it didn’t, you can safely rollback to 8.0.12 while we’re investigating. Can you share the whole stacktrace of the issue ?

3

Hey,

Last version did not fix the issue.

Is it necessary to roll back to v8.0.12 ? I also had an error in v8 (500 instead of 409) which is why I upgraded to 9 ?

Thank you for your quick response.

4

Oh.

9.7.0 was causing an issue initialy, so that was my first guess seeing this issue.

Could you share the stacktrace for the 409, a jam.dev of the issue so we can investigate your issue (We accept them as DM if you consider them private informations), or any informations regarding what you are achieving in Forest that could help locate/reproduce what’s going on ?

Thanks in advance :pray:

5

Hey, I retried after replying to your message and it works ! Did not change anything :man_shrugging:t3:
Anyway thanks for your time and quick messages !

Cheers !

6

Good to know. It’s possible that the process from going from free tier to paying caused a reprocessing on our end that took a bit more time than usual to happen. I’ll check internally with the team, as this is the second time we are encountering this issue.

In any case, thanks for letting me know that it works now on your end :pray: