camunda / camunda/task-testing
Better guidance for a failed start instance
Open
Nobody has claimed this yet.
backlog
enhancement
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
If task testing fails to start an instance, no detailed error is shown, even though it's available on the API.
Describe the solution you'd like
A more detailed error is shown.
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 by tracing the task-testing flow that starts an instance and identify where failures are reported. Check how the API exposes the detailed error, then verify that a failed start displays that detail to the user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100