Output in webhook of workflow are in string format

[JCHacking]

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

[Robban1980]

@JCHacking the same issue is happening when working with EventHandlers enabling the following setting conductor.app.summary-input-output-json-serialization.enabled=true improved on the situation but did not make it work like before the oss releases.

[jeffbulltech]

👋 Hi @JCHacking & @Robban1980

We're currently reviewing open issues in the Conductor OSS backlog, and noticed that this issue hasn't been addressed.

To help us keep the backlog focused and actionable, we’d love your input:

• Is this issue still relevant?
• Has the problem been resolved in the latest version v3.21.12?
• Do you have any additional context or updates to provide?

If we don’t hear back in the next 14 days, we’ll assume this issue is no longer active and will close it for housekeeping. Of course, if it's still a valid issue, just let us know and we’ll keep it open!

Thanks for contributing to Conductor OSS! We appreciate your support. 🙌

Jeff Bull

Developer Community Manager | Orkes

DM on Conductor Slack
Email me!

[Robban1980]

@jeffbulltech I have not had time to check if the input-output-json-serialization.enabled=true setting is still needed or not. I would need to setup a test for it.

[jeffbulltech]

@jeffbulltech I have not had time to check if the input-output-json-serialization.enabled=true setting is still needed or not. I would need to setup a test for it.

Thanks for the update @Robban1980 whenever you have a moment free would you mind checking? I'll ensure the GH issue stays open if so.

[Robban1980]

@jeffbulltech I checked Conductor code for the queue_publisher. The value would still be needed; However, the output is expected to be JSON, however it is a JSON string instead of JSON object because the source if an WorkflowSummary object being serailizes
Example output:

    "workflowType": "bugg_report",
    "version": 5,
    "workflowId": "304fb71a-e2bd-4089-a5b4-5768ad8026ea",
    "startTime": "2025-03-14T03:10:48.073Z",
    "updateTime": "2025-03-14T03:10:48.556Z",
    "endTime": "2025-03-14T03:10:48.556Z",
    "status": "COMPLETED",
    "input": "{}",
    "output": "{\"evaluationResult\":[\"null\"],\"selectedCase\":\"null\"}",
    "executionTime": 483,
    "failedReferenceTaskNames": "",
    "priority": 0,
    "failedTaskNames": [],
    "inputSize": 2,
    "outputSize": 51
  }

In this example you can see the output has been seralized as a JSON string and not a JSON object which would be expected

[jeffbulltech]

@jeffbulltech I checked Conductor code for the queue_publisher. The value would still be needed; However, the output is expected to be JSON, however it is a JSON string instead of JSON object because the source if an WorkflowSummary object being serailizes Example output:

    "workflowType": "bugg_report",
    "version": 5,
    "workflowId": "304fb71a-e2bd-4089-a5b4-5768ad8026ea",
    "startTime": "2025-03-14T03:10:48.073Z",
    "updateTime": "2025-03-14T03:10:48.556Z",
    "endTime": "2025-03-14T03:10:48.556Z",
    "status": "COMPLETED",
    "input": "{}",
    "output": "{\"evaluationResult\":[\"null\"],\"selectedCase\":\"null\"}",
    "executionTime": 483,
    "failedReferenceTaskNames": "",
    "priority": 0,
    "failedTaskNames": [],
    "inputSize": 2,
    "outputSize": 51
  }

In this example you can see the output has been seralized as a JSON string and not a JSON object which would be expected

Thanks for getting back to me @Robban1980 i'll make sure it's prioritized