microsoft / microsoft/durabletask-java
Orchestrator function code failures don't contain any information
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 29
- Forks
- 18
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
When orchestrator function code directly throws an exception, the details of the exception are not logged. Instead, only the following is visible:
Unexpected failure in the task execution
This makes it very difficult to determine the actual cause of the failure.
Expected
Details of the exception should be included in the log message that gets logged by the Functions host.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Java SDK handles exceptions thrown directly by orchestrator functions and where the “Unexpected failure in the task execution” message is logged. Identify the existing logging-related tests, if any, and use them to verify that exception details appear in the Functions host log when the issue is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100