docs: Clarify that a Segment Email's publish up date is optional for scheduled broadcasts#836
Draft
promptless-for-oss wants to merge 1 commit into
Conversation
A published Segment Email with no publish up date is now broadcast immediately, matching how it's shown as active in the UI. The cron docs previously stated a publish up date was required, which is no longer true. Refs mautic/mautic#16493, mautic/mautic#16165
| Starting with Mautic 2.2.0, it's now possible to use cron to send scheduled broadcasts for Channel communications. The current only implementation of this is for Segment Emails. Instead of requiring a manual send and wait with the browser window open while AJAX batches over the send, it's possible to use a command to initiate the process. | ||
|
|
||
| The caveat for this is that the Email must have a published up date and be currently published - this is to help prevent any unintentional Email broadcasts. Just as it was with the manual/AJAX process the message is only sent to Contacts who haven't already received the specific communication. This command sends messages to Contacts added to the source Segments later, so if you don't want this to happen, set an unpublish date. | ||
| The Email must be active for Mautic to broadcast it. The 'Publish at (date/time)' field is optional and acts as a scheduled start date. If you leave it empty, Mautic broadcasts the Email as soon as you turn it on. If you set a future date, Mautic holds the Email back until that date and time. Mautic never broadcasts inactive Emails, which helps prevent unintentional Email broadcasts. Just as with the manual or AJAX process, Mautic only sends the message to Contacts who haven't already received the specific communication. This command sends messages to Contacts added to the source Segments later, so if you don't want this to happen, set an 'Unpublish at (date/time)' date. |
Contributor
Author
There was a problem hiding this comment.
PR #16493 changes EmailRepository::getPublishedBroadcastsQuery() to allow a null publish up date, so a published Segment Email with no publish up date is now broadcast immediately (a future date still holds it back). This makes the prior doc statement that the Email "must have a published up date" incorrect, so I rewrote the paragraph to describe the publish up date as an optional scheduled start date.
Source: mautic/mautic#16493
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
1 participant
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.
Open this suggestion in Promptless to view citations and reasoning process
Corrects the 'Send scheduled broadcasts' cron job section, which stated a Segment Email must have a publish up date to be broadcast. After the optional-start-date change, a published Segment Email with no publish up date is broadcast immediately; a future publish up date holds it back; inactive Emails are never sent. Aligns docs with mautic/mautic#16493 (fixes #16165).
Trigger Events
Tip: Configure how Promptless handles changelogs in Agent Settings 📋