en	Add task

en	Edit task

en	Cancel

en	Scheduled tasks

en	Setup check

en	Information

en	CLI script

en	System is running in Composer Mode

en	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`.

en	Last run

en	automatically

en	Backend types

en	Number of days until removing files

en	Check/uncheck all

en	Class

en	Cron

en	Definition type

en	Interval

en	Cron command

en	Description

en	Email

en	End (HH:MM DD-MM-YYYY)

en	Execute

en	Execute on next cron job

en	Extension

en	Frequency

en	Frequency (seconds or cron command)

en	ID

en	Last Execution

en	Manual

en	manually

en	Name

en	Next Execution

en	Parallel Execution

en	Allow Parallel Execution

en	Server time

en	Sleep time

en	Start (HH:MM DD-MM-YYYY)

en	Storage to index

en	Number of files per run

en	Registered extractors

en	%1$s with priority %2$d

en	Following extractors have been registered and will be used when running this task

en	There currently is no extractor registered. This task will have no effect!

en	Clean all available tables

en	Table to clean up

en	Table: %s

en	All tables

en	Delete entries older than given number of days

en	Database tables

en	Status

en	Type

en	Recurring

en	Single

en	Task group

en	Amount of tasks in this scheduler task group

en	(no task group defined)

en	Amount of tasks that are not assigned to any scheduler task group

en	Tasks without registered classes

en	Amount of tasks without found class

en	Schedulable Command. Save and reopen to define command arguments

en	Save and create new task

en	Add option

en	The task could not be added.

en	The task was added successfully.

en	The script to execute the Scheduler from the command line is: <strong>"%s scheduler:run"</strong>.

en	The webserver user is allowed execute this script.

en	The webserver user is not allowed to execute this script.

en	Are you sure you want to delete this task?

en	The task could not be deleted.

en	The task was successfully deleted.

en	The end date is before the start date.

en	Task "%s" with uid "%s" has been executed.

en	Invalid frequency. Please enter either a number of seconds or a valid cron command. The cron parser said: %1$s [code: %2$d].

en	The information about the last execution of the Scheduler is incomplete.

en	This is the list of all available tasks in this TYPO3 installation. Click on the icon at the far right to directly create a new scheduled task of the chosen type.

en	Invalid frequency. Please enter either a number of seconds or a valid cron command.

en	Please enter a sleep time greater or equal to 0 (zero).

en	The Scheduler was last started (%1$s) on %2$s at %3$s and ended on %4$s at %5$s.

en	A running task may not be deleted.

en	A running task may not be edited.

en	The task is not running. There are no executions to unmark.

en	Please enter an email address.

en	No frequency was defined, either as an interval or as a cron command.

en	The Scheduler has never yet run or the information about the last run has been lost.

en	There are currently no task classes available at all. To be able to create new tasks, you must either enable the samples provided by the Scheduler or install some other extension that relies on the Scheduler.

en	The selected task class could not be found. You should probably contact the task's developers.

en	No tasks defined yet.

en	Task "%s" with uid "%s" has not been executed.

en	Execution of task "%1$s" failed with the following message: %2$s

en	The execution failed, but the error message could not be retrieved (it was probably too large). Sorry.

en	Execution failed: %1$d, %2$s

en	Please define a start date.

en	Start date is invalid.

en	End date is invalid.

en	Number of days is invalid.

en	Some of the selected cache backends do not exist. Please select valid backends only.

en	Please select at least one cache backend.

en	<strong>The following tasks can not be executed. No related class could be found for none of the following listed tasks.</strong> You should consider reinstalling the extension that provided them or simply deleting the tasks. 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).

en	The current class (%s) could not be found. Change it below or consider deleting this task altogether.

en	%s registered scheduler tasks can not be executed

en	<a href="#scheduler-task-group-missing">Please check the erroneous tasks!</a>

en	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.

en	Current server time is %s.

en	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.

en	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).

en	The task could not be marked as non-running.

en	The task was successfully marked as non-running.

en	The requested task (UID: %d) was not found.

en	The task was updated successfully.

en	The task could not be updated.

en	Some of the selected database tables do not exist. Please select only valid tables.

en	Please select at least one database table.

en	Command with identifier "%s" has not been registered.

en	Error parsing current set of arguments: "%s".

en	Error parsing current set of options: "%s".

en	Argument "%s" is mandatory

en	None

en	Status

en	Progress

en	disabled

en	failure

en	late

en	running

en	scheduled

en	Task

en	TYPO3 Scheduler administration module

en	Run task

en	Run task on next cron job

en	Scheduler test task

en	The Scheduler test task just sends a mail to a given email address. It is designed to be used for testing purposes.

en	Scheduler sleep task

en	This task does nothing but put PHP to sleep for a number of seconds. It is designed to test multiple executions.

en	Caching framework garbage collection

en	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.

en	[OBSOLETE] File Abstraction Layer: Indexing job

en	Runs indexing tasks based on an indexing configuration and a storage/folder information.

en	File Abstraction Layer: Update storage index

en	Updates the Index/Cache Data of a Storage; only needed if changes to the storage are possible outside the backend (FTP, RemoteStorages).

en	File Abstraction Layer: Extract metadata in storage

en	Extracts metadata for all files in storage which have been changed since last run.

en	Table garbage collection

en	Task to delete old entries from specific tables like sys_log. Use $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['scheduler']['tasks']['tx_scheduler_TableGarbageCollection']['options']['tables'] to configure tables. Refer to the manual for more details.

en	Fileadmin garbage collection

en	This task empties all "_recycler_" folders below fileadmin. This helps free some space in the file system.

en	Execute console commands

en	Allows regular console commands to be configured and executed through the scheduler framework.

en	Optimize MySQL database tables

en	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.

en	Anonymize IP addresses in database tables

en	This task anonymizes the IP addresses to enforce the privacy of the persisted data.

en	Table to anonymize

en	Table: %s after %s days

en	All tables

en	Handle entries older than given number of days

en	Mask level

en	Last byte for IPv4 / Interface ID for IPv6

en	Last 2 bytes for IPv4 / Interface & SLA ID for IPv6

en	Every day-of-week from Monday through Friday at 09:00 and 15:00

en	Every 2 hours

en	Every 20 minutes

en	Every Tuesday at 07:00

en	It seems the Scheduler has never yet run. Please check your <a href="%1$s">configuration</a>.

en	Last Scheduler run

en	%1$s at %2$s, Duration %3$s, (started %4$s)