conductor-oss/conductor

[FEATURE]: JSON JQ Transform Task – Enhanced Error Handling

Open

#419 opened on Mar 14, 2025

View on GitHub
 (0 comments) (0 reactions) (2 assignees)Java (894 forks)batch import
featurehelp wanted

Repository metrics

Stars
 (31,816 stars)
PR merge metrics
 (Avg merge 7d 14h) (34 merged PRs in 30d)

Description

Describe the Feature Request

Currently, the task applies a JQ query expression (queryExpression) to transform JSON input​. If the JQ expression is invalid or doesn’t match the input, the workflow task can fail with a generic error. The system does include an error field in the task output for failures​

Describe Preferred Solution

when a JQ query fails to parse or returns no results, the task could populate output.error with a message describing the issue (syntax error details or “no results from query”), rather than a vague failure.

Describe Alternatives

--

Contributor guide

Research direction
Inspect the existing error handling in the JQ transform task, locate where the JQ query is executed, and modify the code to catch specific exceptions (e.g., parse errors, no results) and populate the output error field with a descriptive message. Ensure you update the relevant test files.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75