[DOCS] Clarify changed logger instantiation in scheduler tasks

Resolves: #90415
Releases: master, 9.5
Change-Id: Icb403e6ef2892ff7988a34652d6cdfa8f8bd1cfd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63601


Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Benni Mack <benni@typo3.org>

typo3/sysext/core/Documentation/Changelog/9.5.x/Important-86785-CallingSchedulerTaskThrowsLoggerError.rst → typo3/sysext/core/Documentation/Changelog/9.5.x/Important-86785-ExcludeLoggerFromSerialisationForSchedulerTasks.rst

 .. include:: ../../Includes.txt
 
-=========================================================================================
-Important: #86785 - Calling scheduler command on CLI throws error if not in /var/www/html
-=========================================================================================
+================================================================================
+Important: #86785 - Exclude logger from serialisation on save for scheduler task
+================================================================================
 
 See :issue:`86785`
 
 Description
 ===========
 
-Calling the scheduler command on CLI or in backend throws an error, if the TYPO3 CMS installation is not running in @/var/www/html/@.
+Calling the scheduler command on CLI or in backend throws an error, when you
+created a scheduler task in one environment (for example one where TYPO3 was
+running in `/var/www/html`) - and then you take that database and move to another
+environment (where TYPO3 is running somewhere else, for example in
+`/var/www/something`). Trying to execute any task in the scheduler resulted
+in an error, because the Logger instance that was stored with the task in the
+database had the wrong log file path.
 
-After saving the scheduler task, the logger instance is serialized to the database with absolute paths (FileWriter::class).
-Exclusion of the logger instance from the record during save to database prevents that error.
+To get rid of that problem, the logger is no longer stored with the task in the
+database, but instead re-instantiated when the task is run
+(which means it checks for correct paths on the current environment).
+
+Exclusion of the logger instance from the record during save to database
+prevents the error.
 
 Impact
 ======