@@ -194,6 +194,13 @@ Then, define the trigger date/time using the same syntax as the
194
194
195
195
RecurringMessage::cron('* * * * *', new Message());
196
196
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
+
197
204
.. tip ::
198
205
199
206
Check out the `crontab.guru website `_ if you need help to construct/understand
@@ -257,10 +264,6 @@ For example::
257
264
The day of month range is ``1-28 ``, this is to account for February
258
265
which has a minimum of 28 days.
259
266
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
-
264
267
Periodical Triggers
265
268
~~~~~~~~~~~~~~~~~~~
266
269
@@ -353,6 +356,11 @@ Finally, the recurring messages has to be attached to a schedule::
353
356
}
354
357
}
355
358
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
+
356
364
Consuming Messages (Running the Worker)
357
365
---------------------------------------
358
366
@@ -371,11 +379,6 @@ the Messenger component:
371
379
.. image :: /_images/components/scheduler/generate_consume.png
372
380
:alt: Symfony Scheduler - generate and consume
373
381
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
-
379
382
Debugging the Schedule
380
383
----------------------
381
384
0 commit comments