How to get SC to return success regardless of Exec status?

[transcoderm]

@transcoderm

think that how I used to do. I still believe there’s way to completely do this from SC though. Since my main issue is with email execution, I’m gonna try using insert query, then, using scheduler from server side to execute mailer base on the query with status not sent.

I did this. I believe the step was right except scheduler seems not work with mailer. Got this error:

 (node:6040) UnhandledPromiseRejectionWarning: TypeError: this.req.get is not a function
    at App.send (C:\laragon\www\nodejs\site\lib\modules\mail.js:74:41)
    at App._exec (C:\laragon\www\nodejs\site\lib\core\app.js:429:57)
    at App._exec (C:\laragon\www\nodejs\site\lib\core\app.js:400:28)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async App.exec (C:\laragon\www\nodejs\site\lib\core\app.js:369:9)
    at async App.exec (C:\laragon\www\nodejs\site\lib\modules\core.js:169:13)
    at async App._exec (C:\laragon\www\nodejs\site\lib\core\app.js:429:30)
    at async App._exec (C:\laragon\www\nodejs\site\lib\core\app.js:400:17)
    at async App.exec (C:\laragon\www\nodejs\site\lib\core\app.js:369:9)
    at async App.repeat (C:\laragon\www\nodejs\site\lib\modules\core.js:72:17)
(node:6040) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)

I've tested few scenario, within repeat, using single query, with Exec, directly create mailer there, with Try and Catch, all consistently returned this error when there's email in the step. Other step like update works without issue.

The steps:

1. Query status == 0
2. Email based on Query
3. Update status = 1

May I have confirmation here if scheduler does support mailer component of not. Or which step I might did wrongly. I need assistance on this @patrick.

And @sid if you have spare time feel free to test it as well.

Update: Findings after more tests:

• mail delivers when body is set to static and not html.
  "body": "{{query_mailer_list.mail_body}}",
  "contentType": "html"
• mail with Exec > Library (with param) doesn't work (error above)

So probably has something to do with existing bugs, I dunno..

Update#2:
Indeed, there's no issue with Exec. After I changed the Mail Send setting in the Library > Format: Text the email goes through. So the culprit here is Email Format: HTML.