conductor-oss/conductor

Output in webhook of workflow are in string format

Open

#132 opened on Apr 15, 2024

View on GitHub
 (6 comments) (2 reactions) (1 assignee)Java (31,816 stars) (894 forks)batch import
bughelp wanted

Description

Describe the bug When I receive a workflow status update, I get the workflow output in string format instead of json format.

Details Conductor version: 3.19.0

To Reproduce Steps to reproduce the behavior:

  1. Configure conductor with webhook feature
  2. Create workflow
  3. Start workflow
  4. See request sended has output in string format instead json

Expected behavior Output everywhere should be json

Contributor guide

Tech stack
javarest api
Domain
apibackend
Issue type
bug
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.
clear
Prerequisites
Javawebhook conceptsJSON serialization
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the webhook payload serialization process in the Conductor source code. Look for files that convert workflow output to JSON format, such as in the webhook controller or service layer. Check if the output is being converted to string prematurely or if there is a missing JSON serialization step. Examine the ObjectMapper configuration used for JSON serialization.