blocks|key|102398|text|您需要编写一个脚本作为包装器，以决定是否每隔45分钟执行一次实际命令。即0，45，30+(=+45+%2B+45+-+60)，15+(=+30+%2B+45+-+60)，0+(=+15+%2B+45+-60)。因此，运行脚本的分钟数应为0,15,30,45。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|102399|在shell脚本中，命令date+%2B%25M可能会有所帮助。|102400|entityMap^0|34|A|0|C|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

You need to write a script as a wrapper to decide if the actual command shall be executed at every 45 minutes. That's 0, 45, 30 (= 45 + 45 - 60), 15 (= 30 + 45 - 60), 0 (= 15 + 45 - 60). so, the minutes to run the script shall be <code>0,15,30,45</code>.

The command <code>date +%M</code> may be helpful in the shell script.

blocks|key|4608961|text|与node-cron相比，我更熟悉cron，但我已经快速浏览了一下文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4608962|如果我理解正确的话，node-cron使用的语法与cron使用的语法类似，但有一个额外的“秒”字段。因此，cron作业可能具有以下内容：|4608963|#+min+hour+mday+month+wday+command
*/15++*++++*++++*+++++*++++some-command|code-block|syntax|javascript|4608964|要将some-command安排为每15分钟运行一次，node-cron将使用类似的语法来指定运行时间：|style|CODE|4608965|'0+*/15+*+*+*+*'|4608966|(带有指定秒的附加字段)，但它执行指定的JavaScript函数，而不是外部命令。|4608967|在标准cron中，没有指定每45分钟运行一次作业的语法。0/45+*+*+*+*的规范将每小时运行一次作业两次，运行时间分别为0和45分钟。要每45分钟(在00:00，00:45，01:30，02:+15，...，即每天32次)运行一次作业，您必须将其安排为每15分钟运行一次，然后调用一个脚本来检查当前时间，以决定是否执行任何操作。|4608968|或者，您可以编写一个详尽的列表，列出您希望作业运行的所有时间：|4608969|+0++0+*+*+*+some-command
45++0+*+*+*+some_command
30++1+*+*+*+some_command
15++2+*+*+*+some_command
#+28+lines+omitted|4608970|我肯定想写一个脚本来生成这个列表。|4608971|(这是可行的，因为24小时恰好是45分钟的倍数。您不能以这种方式每35分钟运行一次。)|4608972|类似的方法应该适用于node-cron。将函数安排为每15分钟运行一次，并调用一个检查当前时间的函数，以决定是否运行。例如，您可以检查模数为45的午夜以来的分钟数是否为零。(您可能希望在调度不准确的情况下允许较小的差异。)|4608973|我对JavaScript的了解还不够深入，无法建议编写此函数的最佳方法，但它应该相当简单。|4608974|或者编写32行代码来指定您希望它运行的所有时间。|4608975|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ncb000gt/node-cron^0|1|9|0|0|0|0|2|C|0|0|0|S|C|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@$A|1H|B|1I|1|1J]]|C|$]]|$1|D|3|E|5|6|7|1K|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1L|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1M|8|@$A|1N|B|1O|M|N]]|9|@]|C|$]]|$1|O|3|P|5|H|7|1P|8|@]|9|@]|C|$I|J]]|$1|Q|3|R|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1R|8|@$A|1S|B|1T|M|N]]|9|@]|C|$]]|$1|U|3|V|5|6|7|1U|8|@]|9|@]|C|$]]|$1|W|3|X|5|H|7|1V|8|@]|9|@]|C|$I|J]]|$1|Y|3|Z|5|6|7|1W|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1X|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|14|3|15|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|20|8|@]|9|@]|C|$]]|$1|18|3|-4|5|6|7|21|8|@]|9|@]|C|$]]]|19|$1A|$5|1B|1C|1D|C|$1E|1F]]]]

I'm more familiar with cron than with <a href="https://github.com/ncb000gt/node-cron" rel="noreferrer">node-cron</a>, but I've taken a quick look at the documentation.

If I understand it correctly, node-cron uses a syntax similar to that used by cron, but with an additional "seconds" field. So where a cron job might have:

<pre><code># min hour mday month wday command
*/15 * * * * some-command
</code></pre>

to schedule <code>some-command</code> to run every 15 minutes, node-cron would use a similar syntax to specify the time to run:

<pre><code>'0 */15 * * * *'
</code></pre>

(with an additional field to specify seconds), but it executes a specified JavaScript function, not an external command.

In standard cron, there is no syntax to specify running a job every 45 minutes. A specification of <code>0/45 * * * *</code> would run a job twice each hour, at 0 and 45 minutes after the hour. To run a job every 45 minutes (at 00:00, 00:45, 01:30, 02:15, ..., i.e., 32 times per day) you'd have to schedule it to run every 15 minutes, and then invoke a script that checks the current time to decide whether to do anything.

Or you can write an exhaustive list of all the times you want the job to run:

<pre><code> 0 0 * * * some-command
45 0 * * * some_command
30 1 * * * some_command
15 2 * * * some_command
# 28 lines omitted
</code></pre>

I'd definitely want to write a script to generate this list.

(This is workable because 24 hours happens to be a multiple of 45 minutes. 
 You couldn't run something every 35 minutes this way.)

A similar approach should work for node-cron. Schedule the function to run every 15 minutes, and invoke a function that checks the current time to decide whether to run. For example, you can check whether the number of minutes since midnight modulo 45 is zero. (You might want to allow for a small variance in case the scheduling is not exact.)

I don't know JavaScript well enough to suggest the best way to write this function, but it should be reasonably straightforward.

Or write 32 lines to specify all the times you want it to run.

blocks|key|4609001|text|使用cron+npm+moduel，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609002|var+cronJob+=+require('cron').CronJob;++
var+job+=+new+cronJob({+
++++cronTime:'0+*/45+*+*+*+*',+
++++onTick:+function(){
++++++++var+my_date+=+new+Date();
++++++++var+tomorrow_date+=+my_date.getFullYear()+%2B+"-"+%2B+('0'%2B(my_date.getMonth()%2B1))+%2B+"-"+%2B+(my_date.getDate()%2B1)
++++++++var+condition+=+[{},{$set:+{'plannedDeliveryDate'+:tomorrow_date+%2B'T00:00:00.000Z'}}]
++++++++dbQuery.updateMany(orderModel,+condition,+function(err,+result){
++++++++++++if(result.nModified+==+result.n)+console.log(err,+result)
++++++++})
++++},
++++start:true,
++++timeZone:'Asia/Kolkata'
});
job.start();|code-block|syntax|javascript|4609003|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

use cron npm moduel something like this

<pre><code>var cronJob = require('cron').CronJob; 
var job = new cronJob({ 
 cronTime:'0 */45 * * * *', 
 onTick: function(){
 var my_date = new Date();
 var tomorrow_date = my_date.getFullYear() + "-" + ('0'+(my_date.getMonth()+1)) + "-" + (my_date.getDate()+1)
 var condition = [{},{$set: {'plannedDeliveryDate' :tomorrow_date +'T00:00:00.000Z'}}]
 dbQuery.updateMany(orderModel, condition, function(err, result){
 if(result.nModified == result.n) console.log(err, result)
 })
 },
 start:true,
 timeZone:'Asia/Kolkata'
});
job.start();
</code></pre>

blocks|key|4609030|text|我在45秒的间隔内尝试了这个字符串，它工作得很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609031|'*/45+*+*+*+*+*'|code-block|syntax|javascript|4609032|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I tried this string for a 45-second interval and it works well:

<pre><code>'*/45 * * * * *'
</code></pre>

blocks|key|102483|text|你可以参考cronr，它支持所有的宏模式，并提供在线演示cronr+--+online+demo|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|102484|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ryuever/cronr|1|https://ryuever.github.io/cronr/^0|5|5|0|S|K|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You can refer to <a href="https://github.com/ryuever/cronr" rel="nofollow noreferrer">cronr</a>, it supports all the macro pattern and provides online demo <a href="https://ryuever.github.io/cronr/" rel="nofollow noreferrer">cronr -- online demo</a>

blocks|key|102505|text|你可以使用node-reel，它更具可读性、直截了当、令人敬畏。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|102506|const+reel+=+require('node-reel')

reel().call(()+=>+{
++++console.log(Date.now());
}).everyFortyFiveMinutes().run()|code-block|syntax|javascript|102507|https://github.com/shakee93/node-reel|102508|entityMap|0|LINK|mutability|MUTABLE|url^0|5|9|0|0|0|11|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|L]]]]

you can use <code>node-reel</code> which is more readable, straight forward and awesome .

<pre><code>const reel = require('node-reel')

reel().call(() =&gt; {
 console.log(Date.now());
}).everyFortyFiveMinutes().run()
</code></pre>

<a href="https://github.com/shakee93/node-reel" rel="nofollow noreferrer">https://github.com/shakee93/node-reel</a>

blocks|key|4609146|text|最近(27%7C01%7C22)在我的项目中使用了Node+Cron|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4609147|const+TaskSchedulerTimeInterval+=+45;

//+Runs+a+job+for+every+45+mins+asynchronously
const+fetchYoutubeAPIScheduler+=+()+=>+{
++++try+{
++++++++nodeCron.schedule(`*/${TaskSchedulerTimeInterval}+*+*+*+*`,+async+()+=>+{
++++++++++++console.log('Running');
++++++++})
++++}+catch+(error)+{
++++++++console.log('error+=',+error);
++++}
};|code-block|syntax|javascript|4609148|潜在的含义(喜欢别人的解释，所以在一篇文章中一起引用他们)：|4609149|#sec+min+hour+monthday+month+weekday
*/15++*++++*+++++*+++++++*+++++++*++|4609150|上面的示例每15秒运行一次|4609151|每个字段的范围：|4609152|Sec:+0-59
Min:+0-59
Hour:+0-23
monthday(Day+of+Month):+1-31
Months:+0-11
weekDay(Day+of+Week):+0-6|4609153|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Just recently (27|01|22) used Node Cron in my project
<pre><code>const TaskSchedulerTimeInterval = 45;

// Runs a job for every 45 mins asynchronously
const fetchYoutubeAPIScheduler = () =&gt; {
 try {
 nodeCron.schedule(`*/${TaskSchedulerTimeInterval} * * * *`, async () =&gt; {
 console.log('Running');
 })
 } catch (error) {
 console.log('error =', error);
 }
};
</code></pre>
Underlying Meaning (loved the explanations given by others, so referencing them together in one post) :
<pre><code>#sec min hour monthday month weekday
*/15 * * * * * 

</code></pre>
Above example runs every 15 secs
range of each field:
<pre><code>Sec: 0-59
Min: 0-59
Hour: 0-23
monthday(Day of Month): 1-31
Months: 0-11
weekDay(Day of Week): 0-6
</code></pre>

I'm using node-cron to run scheduled jobs.
I want the jobs to run every 45 minutes, but its acting strangely

Here's the pattern I'm using

<code>'00 */45 * * * *'</code>

I started my script at 
<code>Tue Jun 17 2014 08:17:39 GMT+0000 (GMT)</code>

Here's are the first couple of times the job was executed

<code>1. Tue Jun 17 2014 08:45:03 GMT+0000 (GMT)</code>

<code>2. Tue Jun 17 2014 09:00:01 GMT+0000 (GMT)</code>

<code>3. Tue Jun 17 2014 09:45:02 GMT+0000 (GMT)</code>

This is definitely not what I expected or want.
All I want is to run the Jobs every 45 minutes.
Can anyone help me with the pattern?
Thanks :)

Run Cron Job every 45 minutes with Node-Cron

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我使用node-cron来运行计划的作业。我希望作业每隔45分钟运行一次，但它的行为很奇怪下面是我正在使用的模式'00 */45 * * * *'我的脚本是从Tue Jun 17 2014 08:17:39 GMT+0000 (GMT)开始的下面是该作业执行的前几次1. Tue Jun 17 2014 08:45:03...

问使用Node-Cron每45分钟运行一次Cron作业
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Node-Cron每45分钟运行一次Cron作业EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Node-Cron每45分钟运行一次Cron作业
EN