Hello!
This has a workflow definition. The monthly schedule is adjusted once. Then I run the complement here. I found that I still run by day.
Timer management.

Workflow parameter definition

Can we make it easy to explain the flow logic of the complement?
您好!
这个有个工作流定义 每月调度定时调一次. 然后我这边运行 补数. 发现还是按天跑的.
定时器管理.

工作流参数定义

大佬们 能补能方便讲解下补数的流程逻辑?
We are sorry for that situation. Complements are designed to run in the interval of days, where they are run every day and cannot be checked for timing tasks, but we are considering optimizing the design.If you have a better idea, please let us know.
My previous practice.
For example, the complement date is 2018.01.01 ~ 2019.05.04
我以前的做法。
比如补数日期 2018.01.01 ~ 2019.05.04
一. 若工作流设置了定时器. 就要根据定时器去重跑
1.1 ,若定时器为每月(0 10 8 1 * ? *) 则补数/重跑 时间参数应该为 2018.01.01 08:10:00, 2018.02.01 08:10:00 ...... 2019.05.01 08:10:00
1.2 若定时器为每日(0 10 8 * * ? *) 则补数/重跑 时间参数应该为2018.01.01 08:10:00,2018.01.02 08:10:00 , 2018.01.03 08:10:00 。。。。2019.05.04 08:10:00
1.3 若定时器为每小时(0 10 * * * ? *) 则补数/重跑 时间参数应该为 2018.01.01 00:10:00,
2018.01.01 01:10:00 。。。
1.4 每分钟类似于上面
但是涉及其他复杂的调度周期频率 目前我也没想好 😅
二.若工作流没有设置定时器 就按目前的 按天补数.
I also encountered the same complement problem here.
Ask, is this feature perfected in version 1.0.3?
我这里也碰到同样的补数问题。
问下, 是在1.0.3版本里完善这个功能吗
we would do this after version 1.0.3, because there aren't enough people to do this.
so we strongly need some people interested in Easy Scheduler to contribute code.
yes, if who interested in this issue, please leave a message,
and if nobody want to implement this, we will do it the next version after 1.0.3!
This complement function is too important, suggesting a practice, such as the complement date 2018.01.01 ~ 2019.05.04 running logic:
这个补数功能太重要了,建议一种做法,比如补数日期 2018.01.01 ~ 2019.05.04 运行逻辑:
is there any plan for this feature? i think Supplement Data per hour is important to many users, or we must run a workflow and wait, then run the next workflow, for many times.
I will implement this feature
@zixi0825 when will we be able to use this feature?
@zixi0825 when will we be able to use this feature?
the dev branch has implemented,you can try it