From c84b383d01857e04c34d82cff3b6cfb6860411ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Itay=20Kr=C3=A4mer?= Date: Tue, 1 Sep 2026 14:48:45 +0200 Subject: [PATCH] [DOCS] Remove manual execution notes --- Documentation/Usage/SentryMonitors.rst | 5 +---- Documentation/Usage/TaskExecution.rst | 15 --------------- 2 files changed, 1 insertion(+), 19 deletions(-) diff --git a/Documentation/Usage/SentryMonitors.rst b/Documentation/Usage/SentryMonitors.rst index ce45623..a5dc144 100644 --- a/Documentation/Usage/SentryMonitors.rst +++ b/Documentation/Usage/SentryMonitors.rst @@ -5,10 +5,7 @@ Sentry monitors =============== The extension creates a Sentry cron monitor for each TYPO3 Scheduler task. -Starting a task manually in the TYPO3 Scheduler backend creates an additional -monitor instead of using the monitor for scheduled executions. Running the task -with ``scheduler:execute`` uses the scheduled monitor. Existing and newly added -tasks require no task-specific Sentry code. +Existing and newly added tasks require no task-specific Sentry code. Monitor identity ================ diff --git a/Documentation/Usage/TaskExecution.rst b/Documentation/Usage/TaskExecution.rst index a66b4a2..e16f078 100644 --- a/Documentation/Usage/TaskExecution.rst +++ b/Documentation/Usage/TaskExecution.rst @@ -25,21 +25,6 @@ A developer or operator can run one configured Scheduler task by UID: vendor/bin/typo3 scheduler:execute --task= -``scheduler:run`` and ``scheduler:execute`` use the same Sentry monitor for the -same task. - -Manual execution in the TYPO3 backend -===================================== - -Starting a task manually in the TYPO3 Scheduler backend creates an additional -Sentry cron monitor instead of using the monitor for its scheduled executions. - -.. important:: - - The extension monitors a console command only when it runs as a configured - TYPO3 Scheduler task. Running a Symfony command directly does not pass - through this extension. - Check-in results ================