Wishlist: Day Granularity for Action Trigger
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
Right now the action/trigger system uses a utility to convert the processing delay and max validity to seconds from now.
So the example overdue notice of 7 days to max 8 days overlaps two days depending on when you set the cron to run. If you set the cron to run at noon for some reason then the range would be from noon 7 days ago to noon 8 days ago.
Most of our A/T work is based on things just being on X day at any time. It would be nice to be able to flag an A/T so that the processing delay is treated more like a psql ::date select.
So:
Today: 2021-07-21
A/T set for -2 days and day granularity with due_date hook
Every circ still checked out that was due on 2021-07-19 is processed
Right now you can get close with making sure crons are at a day edge but depending on clock skew or system load there is potential that something might be missed or the times it runs varies.
This also helps 24 hour libraries where they may want to send a notice mid-day but only get rows that match a single day 00:00:00 - 24:59:59.
Changed in evergreen: | |
importance: | Undecided → Wishlist |
tags: |
added: actiontrigger removed: wishlist |