Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The start time in the schedule is not strictly followed #105

Open
kangroowl opened this issue Apr 24, 2024 · 0 comments
Open

The start time in the schedule is not strictly followed #105

kangroowl opened this issue Apr 24, 2024 · 0 comments

Comments

@kangroowl
Copy link

@stevehu In our tests, we found the start time of in the task definition is not strictly followed. For example, if a task has time unit as DAY and start as 5pm, the task will be triggered on 0am each day instead of 5pm. This is quite unexpected. I think it is due to the code is rounding up the start time to the next time unit at

long start = TimeUtil.nextStartTimestamp(TimeUnit.valueOf(next.value.getFrequency().getTimeUnit().name()), next.value.getStart());
.

I saw a similar issue #22. Is it the same issue or related? You seem have a solution in your mind according to the comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant