Troubleshoot your Hermetiq connection

No builds appear

1. Confirm you are viewing the same Hermetiq project configured in Bazel.
2. If the flags use build:hermetiq, confirm the command includes --config=hermetiq.
3. Verify the BEP instance name and endpoint match the current Quickstart output.
4. Confirm the credential helper exists at the configured workspace path and can run in the local or CI environment.
5. Run a new build and check Build History again.

Authentication errors

For Hermetiq Cloud, regenerate or download the machine credential from the intended project’s Quickstart page. For a customer-managed deployment, obtain the replacement from the deployment administrator. The project encoded in the machine credential must match the project/instance value used by the build.

Also check file permissions, workspace-relative paths, host mappings, and whether the CI environment has the same helper and configuration as local development.

If an administrator rotated the M2M OAuth client or mTLS certificate, every old helper and CI secret is invalid. Replace them before retrying.

Profile analytics are missing

• Confirm the recommended JSON trace-profile flags are active for the invocation.
• Confirm Project Settings has read access to the CAS containing the profile artifact.
• Verify the build completed far enough to publish the profile output.

MCP cannot connect

• For Hermetiq Cloud, sign in to dashboard.hermetiq.io before starting the authentication flow. For customer-managed deployments, sign in to that deployment’s dashboard instead.
• For Claude Code, run /mcp and re-authenticate.
• For Codex, run codex mcp login hermetiq.
• Confirm the client points to https://mcp.cloud-usc1.hermetiq.io or the correct customer-managed MCP endpoint.

Cache or RBE data is missing

BEP alone does not guarantee that cache, completed-action, Buildbarn infrastructure, or cost views will be populated. Confirm the corresponding cache, action-log, metrics, logs, traces, or cost integration is enabled for the project and deployment.

Detailed error guides

Use these symptom-specific references when the initial checks above do not isolate the failure:

• Bazel remote execution deadline exceeded
• Bazel remote cache unavailable
• Buildbarn action stuck in queue
• Buildbarn CAS object not found
• Bazel has no matching toolchains
• Bazel cache misses across machines
• Buildbarn worker is not receiving actions
• Bazel action key changed unexpectedly

Get support

Email support@hermetiq.com with the project name, affected build or invocation ID, approximate time, command type, and the setup step that failed. Do not send private credentials or tokens.