I'm experiencing a comparable problem. The tool operates as a distinct workflow, and its JSON output is accurate. Is there a way to bypass the second ...