Adds better logging for failed processes #52
Merged
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.
This pull request improves error handling and logging for job failures and exception scenarios involving
PolydockAppInstance. The main focus is to ensure that errors are consistently logged both in the application logs and directly on the affectedPolydockAppInstancefor better traceability and debugging.Enhanced error handling and logging:
failed()method to theBaseJobclass to log job failures, including error messages and stack traces, and to append error logs directly to the relatedPolydockAppInstanceusing thelogLinemethod. The handler is designed to never throw exceptions itself, ensuring robust failure logging.PolydockEngineFunctionCallerTraitso that when exceptions occur during app instance processing, errors are now also logged directly to thePolydockAppInstanceusinglogLine, in addition to the existing logging. This is applied for status flow exceptions, process exceptions, and unknown exceptions, ensuring consistent and detailed error tracking on the instance.Minor code style improvements:
BaseJobfor consistency with code style guidelines.