Trigger the DbLogHandler for exceptions in WorkChains run by daemon #908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exceptions that are encountered when ticking processes only got
logged to the daemon log but did not go through the logger of the
process itself and therefore the exception message was not in any
retrievable through the WorkCalculation node.
In the tick_workflow_engine of the daemon, when an exception occurs
in the ticking of the process, a log message is sent to the logger
of the process which should have the DbLogHandler configured, which
will cause the message to end up in the DbLog table. This message
will then be accessible through for example 'verdi work report'