Skip to main content
Participant
September 21, 2026
Question

RoboHelp 2026 command line (--cl) hangs on second execution

  • September 21, 2026
  • 1 reply
  • 10 views

Hello,

I am experiencing an issue with command-line publishing in RoboHelp 2026.03 (latest available release).

I'm trying to automate the publishing of multiple RoboHelp projects as part of a pipeline process in Microsoft Azure DevOps. The goal is to invoke RoboHelp from a batch file or PowerShell script and generate the documentation automatically during the pipeline execution.

For each project, I execute a command similar to:
RoboHelp.exe --cl "C:\Project\Guide1.rhpj" -o "MyPublishProfile" -p "C:\Output\Guide1" -l "C:\Logs\Guide1.html"

The first execution completes successfully and the output is generated correctly.

However, when a second command is executed (for example to publish a different project), RoboHelp remains running and the process never terminates. The command stays pending indefinitely and blocks the script execution. Example:

RoboHelp.exe --cl "Guide1.rhpj" -o "Profile1"
RoboHelp.exe --cl "Guide2.rhpj" -o "Profile2"
RoboHelp.exe --cl "Guide3.rhpj" -o "Profile3"

The first command succeeds, but the second one hangs and never completes.

The same projects can be generated repeatedly through the RoboHelp user interface without any issue: I can publish all three guides one after another from the GUI, so the problem appears to be specific to command-line execution.
 

My questions are:

  1. Is sequential execution of multiple --cl commands officially supported?
  2. Is command-line publishing supported in CI/CD environments such as Azure DevOps?
  3. Is there a recommended cleanup step or process that should be performed between executions?
  4. What is the recommended approach for automatically publishing multiple RoboHelp projects within a build pipeline?

Any guidance would be greatly appreciated.
Thank you.
 

    1 reply

    Jeff_Coatsworth
    Community Expert
    Community Expert
    September 21, 2026

    Based on this old thread - 

     it sounds like batch generation may be busted again in that version you’ve got. I’d contact the RH folks at tcssup@adobe.com to see if there have been reports of cl generation being broken.