@@ -194,6 +194,13 @@ Then, define the trigger date/time using the same syntax as the
194194
195195 RecurringMessage::cron('* * * * *', new Message());
196196
197+ // optionally you can define the timezone used by the cron expression
198+ RecurringMessage::cron('* * * * *', new Message(), new \DateTimeZone('Africa/Malabo'));
199+
200+ .. versionadded :: 6.4
201+
202+ Since version 6.4, it is now possible to add and define a timezone as a 3rd argument
203+
197204.. tip ::
198205
199206 Check out the `crontab.guru website `_ if you need help to construct/understand
@@ -257,10 +264,6 @@ For example::
257264 The day of month range is ``1-28 ``, this is to account for February
258265 which has a minimum of 28 days.
259266
260- .. versionadded :: 6.4
261-
262- Since version 6.4, it is now possible to add and define a timezone as a 3rd argument
263-
264267Periodical Triggers
265268~~~~~~~~~~~~~~~~~~~
266269
@@ -353,6 +356,11 @@ Finally, the recurring messages has to be attached to a schedule::
353356 }
354357 }
355358
359+ .. versionadded :: 6.4
360+
361+ Since version 6.4, you can define your messages via a ``callback `` via the
362+ :class: `Symfony\\ Component\\ Scheduler\\ Trigger\\ CallbackMessageProvider `.
363+
356364Consuming Messages (Running the Worker)
357365---------------------------------------
358366
@@ -371,11 +379,6 @@ the Messenger component:
371379 .. image :: /_images/components/scheduler/generate_consume.png
372380 :alt: Symfony Scheduler - generate and consume
373381
374- .. versionadded :: 6.4
375-
376- Since version 6.4, you can define your messages via a ``callback `` via the
377- :class: `Symfony\\ Component\\ Scheduler\\ Trigger\\ CallbackMessageProvider `.
378-
379382Debugging the Schedule
380383----------------------
381384
0 commit comments