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
Fixes #24701: Add daily schedule for campaign #5594
base: branches/rudder/8.0
Are you sure you want to change the base?
Fixes #24701: Add daily schedule for campaign #5594
Conversation
Commit modified |
99efd2d
to
f4f6c03
Compare
}).withHourOfDay(end.realHour).withMinuteOfHour(end.realMinute).withSecondOfMinute(0).withMillisOfSecond(0) | ||
} | ||
|
||
Some((startDate, endDate)).succeed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want to limit the max span to 20h or so to avoid all the borderline cases when two campaign override (ie, we don't even want to have to wonder what would happen).
At least, it needs to be less than 24h
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment in other PR: it should work. Let it be like that as @VinceMacBuche asked.
I think the doc for system update API needs to be updated to explain the new data type alternative |
Commit modified |
f4f6c03
to
a5e6305
Compare
PR rebased |
a5e6305
to
ab8ce6d
Compare
Commit modified |
ab8ce6d
to
009e3f9
Compare
api doc added |
https://issues.rudder.io/issues/24701