Exception in job should log the trace not only the exception message #848
Description
Is your feature request related to a problem?
When job runs in background and if it fails then it log only the exception message, so it is very difficult to find where is the actual bug. Look this exception message the JSON object must be str, bytes or bytearray, not NoneType but where we don't now.
What do we currently have to do now?
No response
Describe the solution you'd like
It will be great if we log the exception trace that way we can see the actual file and place to fix the bug.
Describe alternatives you've considered
No response
Would this be a breaking change ?
- Yes
Anything else ?
No response