# Cron-plus and jsonata: error in 3.1.0-beta.2

**URL:** <https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892>\
**Category:** General\
**Created:** [17 July 2023 21:15 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892 "2023-07-17T21:15:52Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![greengolfer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/greengolfer/32/28276_2.png) [@greengolfer](https://discourse.nodered.org/u/greengolfer)\
**Post date:** [17 July 2023 21:15 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/1 "2023-07-17T21:15:52Z")

</div>

When using a jsonata payload in cron-plus eg.

 ![Screenshot 2023-07-17 at 23.13.06](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/2/62ea280681db24c569d41662c4e9302e21080c6f.png)

with a basic flow like:

```auto
[
    {
        "id": "5b82d39f1670e2ed",
        "type": "cronplus",
        "z": "8238839dc502e4bd",
        "name": "",
        "outputField": "payload",
        "timeZone": "",
        "persistDynamic": false,
        "commandResponseMsgOutput": "output1",
        "outputs": 1,
        "options": [
            {
                "name": "schedule1",
                "topic": "test",
                "payloadType": "jsonata",
                "payload": "$millis()",
                "expressionType": "cron",
                "expression": "0 */5 * * * * *",
                "location": "",
                "offset": "0",
                "solarType": "all",
                "solarEvents": "sunrise,sunset"
            }
        ],
        "x": 340,
        "y": 1240,
        "wires": [
            [
                "7589755339c740ec"
            ]
        ]
    },
    {
        "id": "7589755339c740ec",
        "type": "debug",
        "z": "8238839dc502e4bd",
        "name": "debug 303",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 550,
        "y": 1240,
        "wires": []
    }
]

```

Produces these errors messages:

`"Deprecated API warning: Calls to RED.util.evaluateJSONataExpression must include a callback. This will not be optional in Node-RED 4.0. Please identify the node from the following stack and check for an update on npm. If none is available, please notify the node author."`

And:

`Error at evaluateJSONataExpression (/usr/src/node-red/node_modules/@node-red/util/lib/util.js:777:18) at Object.evaluateNodeProperty (/usr/src/node-red/node_modules/@node-red/util/lib/util.js:675:18) at sendMsg (/data/node_modules/node-red-contrib-cron-plus/cronplus.js:867:39) at CronPlus._inputCallback (/data/node_modules/node-red-contrib-cron-plus/cronplus.js:1432:17) at /usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:210:26 at Object.trigger (/usr/src/node-red/node_modules/@node-red/util/lib/hooks.js:166:13) at CronPlus.Node._emitInput (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:202:11) at CronPlus.Node.emit (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:186:25) at CronPlus.Node.receive (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:494:10) at /data/node_modules/node-red-contrib-cron-plus/cronplus.js:1686:22`

I guess cron-plus will require some kind of update.

The flow works though.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 July 2023 11:03 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/2 "2023-07-22T11:03:07Z")

</div>

Thanks.

Issue raised: [Error in 3.1.0 beta when payload is a JSONata value · Issue #61 · Steve-Mcl/node-red-contrib-cron-plus · GitHub](https://github.com/Steve-Mcl/node-red-contrib-cron-plus/issues/61)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 July 2023 22:11 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/3 "2023-07-23T22:11:41Z")

</div>

fixed in v2.0.0 released today.

As well as some other new features I have been working on (very slowly) since November 😲

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [24 July 2023 00:25 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/4 "2023-07-24T00:25:03Z")

</div>

Running pi4 with ver 3.02 just updated cron plus and to my horror it now says flow stopped due to missing node. It's the cronplus node I just updated

[Edit] under the node in palette manager it says  
ERR\_REQUIRE\_ESM

[Edit again] tried it on a second pi setup identical to first and it does same thing

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [24 July 2023 00:31 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/5 "2023-07-24T00:31:29Z")

</div>

How can I get back to a working version?  
[edit]  
Tried npm install cron-plus@1.5.7  
Npm install node-red-contrib-cron-plus@1.5.7  
And several other iterations  
None worked

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 July 2023 01:56 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/6 "2023-07-24T01:56:55Z")

</div>

Oh dear. Most odd. I apologise. Must be one of the updated dependencies. I will fix later today.

In the mean time, `npm install node-red-contrib-cron-plus@1.5.7` should work but you must be in run your .node-red directory and you need to restart node-red afterwards

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 July 2023 02:05 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/7 "2023-07-24T02:05:21Z")

</div>

Ps. What version of node JS are you running node-red on?

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [24 July 2023 02:10 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/8 "2023-07-24T02:10:38Z")

</div>

Version 16.20.1

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [24 July 2023 02:11 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/9 "2023-07-24T02:11:01Z")

</div>

Oh and that command worked, thanks

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 July 2023 08:01 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/10 "2023-07-24T08:01:13Z")

</div>

Rolled back the naughty dependency that dropped CommonJS support for ESM.

Just published 2.0.1

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/7/57a3bef7d92b234965055c894eb07004e718c555.png)

It can take up to 30 minutes for the Node-RED catalog to pick up the change. 🤞

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [24 July 2023 10:50 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/11 "2023-07-24T10:50:21Z")

</div>

Installed 2.01 and no error messages

---

<div class="post-metadata">

**Author:** ![greengolfer](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/greengolfer/32/28276_2.png) [@greengolfer](https://discourse.nodered.org/u/greengolfer)\
**Post date:** [24 July 2023 20:13 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/12 "2023-07-24T20:13:25Z")

</div>

Same here. Fixed in 2.0.1.

Great stuff 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 September 2023 14:24 UTC](https://discourse.nodered.org/t/cron-plus-and-jsonata-error-in-3-1-0-beta-2/79892/13 "2023-09-01T14:24:10Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.