# Forest agent stucked in a previous version

**URL:** <https://community.forestadmin.com/t/forest-agent-stucked-in-a-previous-version/6910>\
**Category:** Help me!\
**Tags:** agent\
**Created:** [December 13, 2023, 10:27pm UTC](https://community.forestadmin.com/t/forest-agent-stucked-in-a-previous-version/6910 "2023-12-13T22:27:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fletoxIsHere](https://avatars.discourse-cdn.com/v4/letter/f/ad7895/32.png) [@fletoxIsHere](https://community.forestadmin.com/u/fletoxIsHere)\
**Post date:** [December 13, 2023, 10:27pm UTC](https://community.forestadmin.com/t/forest-agent-stucked-in-a-previous-version/6910/1 "2023-12-13T22:27:08Z")

</div>

## Feature(s) impacted

forest agent

## Observed behavior

having the red banner of update required

## Problem

we did the migration to v8 from v7 a few months ago and was perfectly done, but in this week we rollback the project to a previous release for another issue.  
the problem is when we use the recent release of the project, forest agent version stucked in v7, despite, we are using v8 in the last release of the project.

## Failure Logs

## Context

- Project name: Roby
- Team name: Dev
- Environment name: UAT
- Agent (forest package) name & version: “forest-express-mongoose”: “^8.0.0”,
- Database type: mongoDB

---

<div class="post-metadata">

**Author:** ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)\
**Post date:** [December 14, 2023, 7:33am UTC](https://community.forestadmin.com/t/forest-agent-stucked-in-a-previous-version/6910/2 "2023-12-14T07:33:31Z")

</div>

Hello @fletoxIsHere,

Could you please check the content of your `.forestadmin-schema.json` on the environment on which you have this issue?

The version we are detecting comes from this file. This file is not automatically re-generated when `NODE_ENV=production`. The usual process to update it, is generally to test the upgrade on a development environment, which will update the schema file, and then commit both the code (including `package.json`) AND the schema file containing the changes about version and other changes.

If the schema file references an outdated version, I suggest to re-generate it by launching the agent without `NODE_ENV=production` at least once to force the re-generation, and save this schema for later use.