API Action "Pass Errors" erroneous behaviour when run within Scheduled Action

Wappler Version : 4.9.0
Operating System : MacOS
Server Model: NodeJS
Database Type: N/A
Hosting Type: Docker

Expected behavior

After API Action fails and Pass Errors enabled, further steps within the Scheduled Action should not be executed. This actually makes me wonder, when a standard Server Connect Action comes in and Pass Errors passes the error, do further steps actually run? (edit: just checked, this issue only happens on Scheduled Actions. On normal requests, further steps are not executed, although this might be due to an unrelated error, which I’m opening another bug report)

Actual behavior

Further steps are executed, and an undefined error is thrown in console

App listening at http://localhost:3000
  server-connect:app Executing action step send +0ms
  server-connect:app options: { url: 'http://httpstat.us/500' } +0ms
Error [ERR_UNHANDLED_ERROR]: Unhandled error. (undefined)
    at new NodeError (node:internal/errors:371:5)
    at Job.emit (node:events:379:17)
    at /opt/node_app/node_modules/node-schedule/lib/Invocation.js:277:17
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  context: undefined

This error is not thrown immediately, it’s thrown after all further steps are executed

How to reproduce

Create Scheduled Action to run every minute, with one API Action with Pass Errors checkbox ticked, to this page:

This page will return a 500 Internal Server Error, which will trigger “Pass Errors”

Here an update that should throw the error and stop immediately.

api.zip (1.3 KB) Unzip in lib/modules.

This has been fixed in Wappler 4.9.1

This topic was automatically closed after 2 days. New replies are no longer allowed.