Repository navigation
Conversation
…start Adds a bookings.booking_reminder template trigger plus a scheduled sweep that emails the booking owner ahead of the booking starting. Reminders are configured as a list of offsets in minutes before the start, checked by a cron sweep, since a cron entry alone cannot express "3 days before an arbitrary booking start". A grace window stops stale reminders being sent after downtime, bookings created after their reminder moment and checked-in bookings are skipped, and each reminder is sent once with the state persisted in the driver status.
Contributor
Author
|
CI notes for this branch:
Local validation: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded by #638, which carries this work plus the review fixes (reminder attachments, approver merge fields, owner-flag zone skip, network credentials removed from the trigger) and the added spec coverage (cron-driven sweep, two offsets on one booking, locker instance, advertised fields vs sent args).