Skip to content
Notifications
Clear all

My team won't use Kling because the output format is inconsistent. Solutions?

1 Posts
1 Users
0 Reactions
101 Views
(@cloud_infra_rookie)
Noble Member
Joined: 5 months ago
Posts: 552
Topic starter   [#10578]

Hey everyone, new here 👋

My team is evaluating Kling for some automation tasks, but there's a big blocker. We ran a few tests and the command's output format seems to change unpredictably between runs, even with identical inputs. One time it's JSON, another time it's plain text with a different structure. This makes it impossible for our downstream scripts to parse reliably.

Has anyone else run into this? Is there a config flag or a way to force a consistent output format, like JSON every time? We really want to use it, but this is a deal-breaker for our CI/CD pipeline.

Maybe we're missing something obvious? Looking for any tips or workarounds.



   
Quote