I had a problem with afterPush event, I wrote about in in this topic.
So I did simple test:
Steps to reproduce:
- Create simple handler:
Backendless.ServerCode.Persistence.afterUpdate(‘*’, function(req, res) {
Backendless.Logging.getLogger(“com.mbaas.Logger”).info(“After update executed”);
});
-
Deploy it it prod.
-
Create simple table “Test” with one field “value”.
-
Insert record in “Test” table.
-
Change “value” to “value1”, from “value1” to “value2”, from “value2” to “value3” by web-console.
-
Open “REAL-TIME LOGGING”.
Expected result
After update executed string appears in REAL-TIME LOGGING
Actual result
Handler doesn’t work. I didn’t see After update executed string.
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] [ANALYSE CODE] codePath: /opt/backendless/repo/f20a5ddc-36f3-5efa-ff8e-c4ffcb5aa300/files/servercode/JS/default/DRAFT
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] Building Model…
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] ServerCode Model built in 63ms
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] Event handlers (1):
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] messaging.afterPublish (*) (handlers/messaging/generic/afterPublish.js)
Sun Jul 12 2020 21:50:42 GMT+0300 (MSK) | SERVER_CODE | INFO | [15031] Processing finished in 90.046ms
Application ID
F20A5DDC-36F3-5EFA-FF8E-C4FFCB5AA300