Ive Recently Upgraded to Forest Admin Pro and now cannot access any of my collections

Help me!
1

Feature(s) impacted

Since Upgrading to Forest Admin Pro, all my collections on production return a 409 error saying that my collection does not exist, however they all still work in development.

Observed behaviour

I keep getting a breaking page on all my collections

Expected behavior

My Collections should be showing and I should have normal functionality.

Context

  • Project name: Airpool
  • Team name: Operations
  • Environment name: Production
  • 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 3 years
2

Hi @vince

Please can you advise here, I see you fixed the same error before (New users getting 409 error).

Our production environment is currently down and our operations team cannot work. We have recently upgraded to pro and this our first experience which is quite disappointing and unreliable.

3

@Steve_Bunlon @jeffladiray @Xavier @GautierD

4

Hello @StreamDevelopers,

Sorry for the delay of the answer, it seems like our bot has an issue and we were not notified of this newly opened topic.

The upgrade to the pro plan does not have any impact on your agent, but I understand your frustration. I’ll do my best to help you out.

To help investigate this issue, do you have any logs in your agents or in your browser that you can share ?

A specific name of a collection where you observe the issue can also help dig into it.

5

Hi Dogan,

Thank you so much for assisting us.

We are getting the same error on every single one of our collections but here is one below:

[{status: 409, detail: “The collection Company doesn’t exist”, name: “collection not found”}]

But in development all is fine, I have checked our .forestadmin-schema.json file and the collections are all listed there

1 Like
6

I see that you have recently upgraded you agent version, was it in hopes to solve this issue ? Where you experiencing this before the upgrade ?

Do you recall when this error started happening ?

7

@dogan.ay

No, we used to be on the free version which we were told was not available anymore and everything was working perfectly (for about three years). We then started the free trial of the pro version on the 6th of January, we used this for a month and it worked perfectly. Yesterday our free trial ended and we then filled in our payment details and upgraded to the normal pro version, as soon as we did this all of our collections then broke.

8

And our development environment continues to work perfectly

9

Sorry if it was not clear, I meant the agent version upgrade, I see that you have upgraded from 9.3.15 to 9.8.0 on your production environment

10

Oh Sorry, Yes Dogan that was in attempt to resolve the issue

11

To continue our investigation, could I ask of you to record using jam.dev the flow and error that you encounter on the frontend :pray:. You can send it to me privately if you do not wish to share it here.

You might as well want to downgrade the agent version to 9.7.0 as I have discovered another unrelated issue on 9.8.0

12

Hi @StreamDevelopers !
It could be easier for us to help through a debug session, could you book a meeting from that link please:
:point_right: https://meetings-eu1.hubspot.com/lionel-bouzonville
Tx!

13

Hi @lionel.bouzonville @dogan.ay

It seems that the downgrade fixed all our issues. Thank you so much :+1:

2 Likes