Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Orchestrator function code failures don't contain any information

Open
#200 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

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.

Description

P1

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.

Dominant language
Java
Stars
29
Forks
18
Avg merge
1d 10h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/durabletask-java

All issues in microsoft/durabletask-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.