Cancel Create group Scheduled tasks Setup check New task New group Group name CLI script System is running in Composer Mode The system is running in composer mode, the path to the `typo3` executable could not be reliably determined. By default, the command to run in composer mode is `vendor/bin/typo3 scheduler:run`. Last run automatically Backend types Number of days until removing files Check/uncheck all Task Cron Definition type Interval Cron command Description Email End (HH:MM DD-MM-YYYY) Start at Run periodically until Execute Execute on next cron job Frequency Frequency (seconds or cron command) ID Last Execution Manual manually Next Execution Parallel Execution Allow Parallel Execution Server time Sleep time Start (HH:MM DD-MM-YYYY) Storage to index Number of files per run Registered extractors %1$s with priority %2$d Following extractors have been registered and will be used when running this task There currently is no extractor registered. This task will have no effect. Clean all available tables Note: Entries from all available tables are deleted based on the table-specific "expirePeriod" option. Table to clean up Table: %s All tables Delete entries older than given number of days Database tables Status Type Run task multiple times? Recurring Single Task group Not assigned to any task group disabled Unused task groups Group Enable group Disable group Edit group Broken tasks Save and create new task Add option Set option Run on CLI The script to execute the Scheduler from the command line is: <strong>"%s scheduler:run"</strong>. The web server user is allowed execute this script. The web server user is not allowed to execute this script. Are you sure you want to delete this task? The task could not be deleted. The task was successfully deleted. The end date is before the start date. Task "%s" with uid "%s" has been executed. Invalid frequency. Please enter either a number of seconds or a valid cron command. The cron parser said: %1$s [code: %2$d]. The information about the last execution of the Scheduler is incomplete. Invalid frequency. Please enter either a number of seconds or a valid cron command. Please enter a sleep time greater or equal to 0 (zero). The Scheduler was last started (%1$s) on %2$s at %3$s and ended on %4$s at %5$s. A running task may not be deleted. A running task may not be edited. The task is not running. There are no executions to unmark. Please enter an email address. No frequency was defined, either as an interval or as a cron command. The Scheduler has never yet run or the information about the last run has been lost. The selected task type must be either "single execution" or "recurring execution". No tasks found There are currently no configured tasks found. You can create a new one. There are currently no tasks available in the system to be configured. Task "%s" with uid "%s" has not been executed. Execution of task "%1$s" failed with the following message: %2$s Scheduling of task "%1$s" failed with the following message: %2$s Toggling disabled state of task "%1$s" failed with the following message: %2$s Stopping task "%1$s" failed with the following message: %2$s The execution failed, but the error message could not be retrieved (it was probably too large). Sorry. Execution failed: %1$d, %2$s Please define a start date. Start date is invalid. End date is invalid. Number of days is invalid. Some of the selected cache backends do not exist. Please select valid backends only. Please select at least one cache backend. The following tasks are broken. If your task doesn't have a registered class, you should consider reinstalling the extension that provided them or simply deleting the task. In case the error is "Cannot unserialize [class]", the announced class must be removed from your task class, as it is not allowed to be used due to security reasons. Please check also if any of the listed tasks have to be recreated manually (which can be necessary after an extension update due to breaking changes or missing migration scripts).]]> Error message %s registered scheduler tasks can not be executed Please check the erroneous tasks.]]> This screen checks if the requisites for running the Scheduler as a cron job are fulfilled. It also displays information about the last run of the Scheduler. Current server time is %s. All dates and times in the Scheduler are measured according to the server's time, as the Scheduler is run purely on the server-side. Are you sure you want to mark this task as not running? Note that this will not stop the actual script (if unsure please refer to the manual). The task could not be marked as non-running. The task was successfully marked as non-running. The requested task (UID: %d) was not found. The task could not be updated. Some of the selected database tables do not exist. Please select only valid tables. Please select at least one database table. Command with identifier "%s" has not been registered. Error parsing current set of arguments: "%s". Error parsing current set of options: "%s". Argument "%s" is mandatory. Task "%s" with uid "%s" has been enabled. Task "%s" with uid "%s" has been disabled. Task "%s" with uid "%s" has been enabled and queued for execution at next scheduler CLI run. Task "%s" with uid "%s" has been queued for execution at next scheduler CLI run. Successfully deleted scheduler group. Failed to delete scheduler group. Invalid Task type Default expire period of %d days, configured for selected table "%s", will be used. None Status Progress disabled disabled by group failure late running scheduled Task TYPO3 Scheduler administration module Run task Run task on next cron job Caching framework garbage collection This task calls the garbage collection of configured caching framework caches which use one of the selected backends. This will free some space in cache backends which do not have an internal garbage collection. In case of the default database backend it is advisable to run this task once a day when the database is mostly idle. [OBSOLETE] File Abstraction Layer: Indexing job Runs indexing tasks based on an indexing configuration and a storage/folder information. File Abstraction Layer: Update storage index Updates the Index/Cache Data of a Storage; only needed if changes to the storage are possible outside the backend (FTP, RemoteStorages). File Abstraction Layer: Extract metadata in storage Extracts metadata for all files in storage which have been changed since last run. Table garbage collection Task to delete old entries from specific tables like sys_log. Fileadmin garbage collection This task empties all "_recycler_" folders below fileadmin. This helps free some space in the file system. Execute console commands Allows regular console commands to be configured and executed through the scheduler framework. Optimize MySQL database tables This task executes "OPTIMIZE TABLE" statements on the selected database tables. This helps to reduce storage space and improve I/O efficiency. Warning: tables will be locked during the optimization process. Anonymize IP addresses in database tables This task anonymizes the IP addresses from specific tables like sys_log to enforce the privacy of the persisted data. Table to anonymize Table: %s after %s days All tables Handle entries older than given number of days Mask level Last byte for IPv4 / Interface ID for IPv6 Last 2 bytes for IPv4 / Interface & SLA ID for IPv6 Command configuration Configure available arguments and options for the command. Every day-of-week from Monday through Friday at 09:00 and 15:00 Every 2 hours Every 20 minutes Every Tuesday at 07:00 configuration.]]> Last Scheduler run %1$s at %2$s, Duration %3$s, (started %4$s) Error Could not create group Enter a group name Edit group name Search for any kind of tasks Unfortunately no scheduler task matches your query, please try a different one. Delete this task group? You can restore it in the module "Recycler". Delete this task? You can restore it in the module "Recycler". {count, plural, one {# task} other {# tasks}} {count, plural, one {# unused task group} other {# unused task groups}}