Publishing errors are logged in EventLogging, but without any technical details, which is usually needed for actual debugging. It will be useful to log the stack trace, too.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | santhosh | T89585 ContentTranslation publishing error handling is too generic | |||
Resolved | santhosh | T94690 log more details about publishing error |
Event Timeline
Comment Actions
Change 204019 had a related patch set uploaded (by Santhosh):
Fix a js error when publishing fails because of unknown reasons
Comment Actions
Change 204019 merged by jenkins-bot:
Fix a js error when publishing fails because of unknown reasons
Comment Actions
Stack trace is logged now, but parsoid gives just 503 for all errors. Parsoid fix for that is tracked at T96239
Keeping this task open till we see proper logging happens in eventlogging database