microsoft / microsoft/durabletask-mssql
Failed functions don't return "Output" in StatusQueryGetURL
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Symptom: In Azure Functions/v4/dotnet-isolated, if an orchestrator fails with an uncaught exception, the StatusQueryGetURI returns no value for "output" - compare with Azure Storage backend which returns the exception details.
Pretty sure this is due to this logic:
https://github.com/microsoft/durabletask-mssql/blob/7843abebe1d4c43dfe66253845ee815e57fa05c4/src/DurableTask.SqlServer/SqlUtils.cs#L274-L286
Which sets the value of output only if the function didn't fail, but sets the exception details to state.FailureDetails in the failure case.
Evaluate whether a change is needed here, to match the Azure Storage backend behavior, or in the durable extensions.
Contributor guide
No contributing guide indexed for this repository
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 with src/DurableTask.SqlServer/SqlUtils.cs at lines 274-286 and trace how StatusQueryGetURI builds output for failed orchestrations. Compare that behavior with the Azure Storage backend and determine whether the provider or durable extensions should change. Done means the SQL backend exposes failure output consistently with the Azure Storage behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100