Skip to Content
MergeLoom MergeLoom Docs

Controller Audit

Controller Audit is the customer-controller view of MergeLoom coordination. It is different from worker execution audit.

Open the customer controller:

https://controller.mergeloom.ai

Then go to Audit or the controller activity view for your workspace.

What Controller Audit Shows

Section titled “What Controller Audit Shows”

Use Controller Audit for:

  • intake polling and manual sync outcomes
  • tickets skipped or denied before a worker starts the job
  • assignment checks and workspace-user enforcement
  • repository routing failures
  • integration sync success or failure
  • queue and job state changes visible to the controller
  • PR/MR creation or update coordination
  • work tracker status/comment update warnings
  • Retry Publish attempts and publish-stage errors

These records are useful when a ticket was never picked up, never routed to a repository, or failed before worker execution started.

What It Does Not Replace

Section titled “What It Does Not Replace”

Controller Audit does not replace worker execution evidence.

For Cloud Hosted, use the customer controller Cloud Audit pages for retained ticket, code, Context Engine, and controller evidence.

For Self Hosted, use the Local Worker UI for Ticket Audit, Code Audit, live streams, and deep worker traces after the job reaches the worker.

Common Checks

Section titled “Common Checks”

If a ticket did not start:

  1. Confirm Scheduled intake is on.
  2. Confirm the work item has the mergeloom label or configured equivalent.
  3. Confirm the work item is in the configured ready state.
  4. Confirm the assignee is an active MergeLoom workspace user when assignment enforcement applies.
  5. Confirm the work item has the correct repo-<alias> routing label when more than one work repository is enabled.

If a PR or MR was not created:

  1. Confirm the worker produced publishable branch artifacts.
  2. Check the Controller Audit for publish-stage provider errors.
  3. Check the code host connection and repository permissions.
  4. Use Retry publish only when the job is eligible and the failure happened during publish.

Related pages: