Skip to main content

Pipelines

My pipeline didn’t generate a wiki.​

Scheduled pipelines that detect no changes since the last update will show a NO DELTAS status and will not generate documentation. To see whether this applies to a particular pipeline, check its detailed logs.

If this doesn’t apply to your wiki, let us know by filing a bug report and we’ll investigate this for you.

My pipeline failed before completion.​

Pipeline failures occur when Komment encounters unexpected errors during code processing. Common reasons include:

  • Users deleting Komment-generated resources in the git repository while a pipeline is running.
  • GitHub API experiencing downtime. You can check its current status here.
  • A bug in our system — help us improve Komment by filing a bug report.

To understand why a specific pipeline failed, check its logs for detailed information.

My pipeline is stuck.​

Large codebases take longer to document, especially if it's Komment's first time analyzing them. Your pipeline might also experience delays during high-demand periods, particularly if you're on the free Plan.

You can always track Komment's real-time progress for any pipeline by checking the Pipeline details. If the real-time statistics aren't updating, or your pipeline's status doesn't change from RUNNING for more than 24 hours, try manually interrupting the pipeline and restarting the run.