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 (31,816 stars) (894 forks)batch import
featurehelp wanted

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

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.
3
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.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaJQ expressionsConductor task structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Examine the existing JQ transform task implementation in the conductor codebase, likely under 'core' or 'task' modules. Identify how the JQ query is currently executed and where errors are handled. Consider using the existing error field in task output to capture specific error messages from JQ parsing failures. Look for any existing JQ library used (e.g., jq engine or similar). Propose changes to catch exceptions and populate output.error with descriptive messages.