Feature #100946
open
Scheduler: More details via mail on failed task
0%
Description
In the mail received on a failed scheduler task it would be helpful to have more information available that helps identifying the problematic task. Currently there's only the stack trace but e.g. not the id of the scheduler task itself. Other informations might be helpful too.
Sure, the failed task is marked as failed in the BE, but that's not a persistent information we can rely on. The subsequent run of that task might have ran smoothly again. And still I might wanna look into that one that failed.
Updated by Philipp Kitzberger about 1 year ago
- Due date set to 2019-02-28
- Start date changed from 2023-06-02 to 2019-02-28
- Follows Feature #87806: Scheduler: Send email on error added
Updated by Philipp Kitzberger about 1 year ago
- Description updated (diff)
- Start date deleted (
2019-02-28) - Complexity set to easy
Updated by Georg Ringer 11 days ago
- Due date deleted (
2019-02-28) - Sprint Focus set to On Location Sprint
Updated by Garvin Hicking 10 days ago
- Status changed from New to Needs Feedback
Might https://review.typo3.org/84152 be related and solved it for you?
Updated by Philipp Kitzberger 3 days ago
@Garvin Hicking, yes, that is kinda related, but not changing the contents of the cronjob MAILTO mail. I'd like to have ID and name of the failed scheduler task included in that mail.
Updated by Garvin Hicking 3 days ago
Philipp Kitzberger wrote in #note-5:
@Garvin Hicking, yes, that is kinda related, but not changing the contents of the cronjob MAILTO mail. I'd like to have ID and name of the failed scheduler task included in that mail.
Do you have an example mail you get and how it looks with the patch above applied? I thought that the stdterr would contain the contents of the error logger, but this is not the case? I don't have a setup where I could easily investigate this, do you happen to know an easy way to make a scheduler task fail and generate the output that is used for a MAILTO command?