temporalio / temporalio/sdk-python
[Feature Request] Make payload conversion errors on workflow input more discriminable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
Describe the solution you'd like
On invalid workflow input, if a bad value is called, the task fails with a runtime error. This should be a better error type that can be set on workflow_failure_exception_types. Consider reusing this exception in any other place that has payload conversion errors provided we are comfortable with the compatibility break of changing an error type.
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 workflow input payload conversion and how workflow_failure_exception_types matches exceptions. Identify the existing runtime error and any other payload-conversion paths; done means invalid input raises a distinct configurable exception, with compatibility implications and tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100