This is working in Development ENV but in production Environment im getting this error. Previously it worked fine
Hello @Amith_T_R ,
Could you provide your project name and forest dependencies please 
It will help us understanding what is going on.
Is there any distinct difference between your development environment and the production one?
Let me know
Project name : admin.golyv.com
There is no difference, now same database also connected in two ENV
Package.json
{
“name”: “admin.golyv.com”,
“version”: “0.0.1”,
“private”: true,
“scripts”: {
“start”: “node ./server.js”
},
“dependencies”: {
“aws-sdk”: “^2.759.0”,
“axios”: “^0.21.0”,
“body-parser”: “1.19.0”,
“chalk”: “~1.1.3”,
“cookie-parser”: “1.4.4”,
“cors”: “2.8.5”,
“debug”: “~4.0.1”,
“dotenv”: “~6.1.0”,
“express”: “~4.16.3”,
“express-jwt”: “5.3.1”,
“forest-express”: “^7.4.0”,
“forest-express-sequelize”: “^6.6.3”,
“morgan”: “1.9.1”,
“mysql2”: “~1.7.0”,
“require-all”: “^3.0.0”,
“sequelize”: “~5.15.1”,
“stripe”: “^8.129.0”,
“uuid-random”: “^1.3.2”
}
}
Do you have any server logs showing the error you could share with us?
Are both projects in development and production use the same forest dependencies?
Let me know
@Guillaume_Cisco
Thanks for your support
The issue started appearing from yesterday 21-jan-2021
All environment using same codes . now using same db also
This is remote environment’s Logs
Thank you @Amith_T_R
What is exactly the version of your forest-express-sequelize dependency?
Could you update them to the last version and tell me if you are still experimenting the issue.
Let me know
I have been able to reproduce your issue with the 6.7.2 version from forest-express-sequelize.
We will fix the issue and tell you when it has been released.
You can downgrade the version to get the correct behaviour.
Thank you
2 Likes
Hello @Amith_T_R ,
Te 6.7.4 version of forest-express-sequelize has been released 
It should have fixed the behaviour you encountered.
Tell me if everything is ok
2 Likes