Vorlage:Cronjobs/en: Unterschied zwischen den Versionen
Haemel (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „Also note that all Cronjobs are queued on the system and processed chronologically. You can find information about the status of a running Cronjob in the respe…“) |
Haemel (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „All counters are reset daily, at 0 o'clock CET.“) |
||
| Zeile 13: | Zeile 13: | ||
Also note that all Cronjobs are queued on the system and processed chronologically. You can find information about the status of a running Cronjob in the respective area. | Also note that all Cronjobs are queued on the system and processed chronologically. You can find information about the status of a running Cronjob in the respective area. | ||
| − | + | All counters are reset daily, at 0 o'clock CET. | |
Aktuelle Version vom 4. Januar 2019, 16:24 Uhr
With the help of Cronjobs, recurring tasks (e.g. import, export and article listing) can be performed at pre-determined times, fully automatic. The number of 'Cronjobs' that can be executed daily, depends on your chosen package. Please mark only the maximum possible number of cronjobs allowed by your package, which will be displayed below. Marked times above that number, will be ignored by the system.
Package / max. Cronjobs per Area *
Free = 3
Starter = 6
Business = 12
Premium = 24
The information applies separately for each import and for each export profile.
Also note that all Cronjobs are queued on the system and processed chronologically. You can find information about the status of a running Cronjob in the respective area.
All counters are reset daily, at 0 o'clock CET.
