Unexpected error when executing smart actions (V8 + Multiple DBs)

Help me!
1

Feature(s) impacted

Two days ago I posted a topic here with some questions I had when including another database in my project. The issue was solved, and later I decided to upgrade the project to V8 since I wanted to take advantage of some features released on load hook and change hook. However, all smart actions give me a 500 error when executed.

Observed behavior

All smart actions show an error like below when executed.

image
image1132×180 10.8 KB

I’d like to point out that the hooks execute as expected given that I successfully load some data (coming from the database) to a dropdown field in the smart action form. On the other hand, the route associated with the smart action does not execute, which makes me think the problem happens in-between, maybe?

Expected behavior

Expected all smart actions to be working properly.

Failure Logs

This is the result after inspecting the page:

image
image1977×167 35.9 KB

Context

  • Project name: parceiros
  • Environment name: development
  • Package Version: 8.0.0 (forest-express-mongoose)
  • Engine: nodejs
  • Engine Version": 10.24.1
2

Hey @nivea :wave:

Could you please share here or as DM:

  • The smart action code (With the route definition, defined in /routes/your_model.js)
  • The Forest action definition (Defined in /forest/your_model.js)

Looking at the error, I’m expecting a difference between your smart action name & the route name used.

Thanks in advance

3

Thanks, I’ve received the file.
Could you also check your agent logs to see if any issue appear there?
And finally, could you send the HTTP request and response that trigger the HTTP 500 ?

Thanks in advance

4

I’m executing the project through docker, so here are the logs presented until I trigger the smart action:

image
image2975×882 304 KB

Also, does the failure log I mentioned above correspond to the HTTP request you are asking for?

5

It does. I would suggest to wrap your smart action code (The one located in /routes) in a try/catch block so you should be able to get more informations of what going on - and why your server is throwing this error 500.

6

I tried doing that, but the problem seems to be that the code in /routes is not even triggered. I tested a console.log() at the beginning of the function and that was not even printed :disappointed:

7

@nivea

Any furthers logs in your chrome browser?
Any specific CORS configuration that could make this fail?
Could you also try the same action without the permissionMiddleware call, just to check if everything works fine without it ?

8

It worked without the permissionMiddleware call.

9

Ok, I’m able to reproduce the issue. It seems like there is an issue with `permissionMiddlewareCreator.smartAction(). I’m opening a ticket on our end, so be sure you’ll be pinged once fixed.

10

All right, I appreciate it :slight_smile:

1 Like
11

Hi @nivea :wave: unfortunately my team mate speak a little fast.
We can’t reproduce. Please can you check if you install the latest version of forest-express-sequelize?

npm ls forest-express-sequelize
// or
yarn list forest-express-sequelize
12

Hey @Arnaud_Moncel

I have not installed this package. After executing the command you suggested, it returns -- (empty).
I just have forest-express-mongoose in my dependencies:

"dependencies": {
    "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.17.1",
    "express-jwt": "6.0.0",
    "forest-express-mongoose": "^8.0.0",
    "mongoose": "~5.8.2",
    "mongoose-bcrypt": "~1.9.0",
    "mongoose-unique-validator": "~2.0.3",
    "morgan": "1.9.1",
    "onesignal-node": "^3.2.1",
    "phone": "^3.1.10",
    "require-all": "^3.0.0"
  }

If it is of any help, I’m attaching the errors shown in the Chrome console.

log_errors.tar (36 KB)

13

Oh yeah you use mongoose sorry about that, So what is the result of the same command using forest-express-mongoose instead of fores-express-sequelize :pray:

14

Can you share with us the request payload and the response of the failing request from your browser network tab please :pray:

15

If I use forest-express-mongoose, it just returns -- forest-express-mongoose@8.0.0.

The request and response from my browser are below:

16

Can you try to update to the latest version which is v8.4.5 and retry ?

17

@Arnaud_Moncel

Upgrading solved the problem. Thanks a lot :pray:

1 Like