Guardian CLI error codes
Important Guardian Agents are available in private preview. Error codes and messages are based on an early build and are subject to change before general availability.
This topic lists the errors that the collibra ai-gov guardian commands can return, what causes each one, and how to fix it.
When a command fails, the CLI prints an error in the following form. The Caused by line, when there is one, carries the message from Python or from the operating system unchanged.
Error: Error [GUARDIAN_SDK_NOT_INSTALLED]: The Collibra SDK is not installed for this interpreter Details: python cannot load the Collibra SDK. Install "collibra-sdk[guardian-injection,guardian-langchain]" into that interpreter. Caused by: ModuleNotFoundError: No module named 'collibra_sdk'
Errors of the sync command
These errors can occur when you download the latest enforcement bundle.
| Error code | Message | Cause and fix |
|---|---|---|
INVALID_UUID_INPUT
|
Not applicable | The --agent-id value isn't a valid UUID. Check the value. |
SYNC_AGENT_NOT_FOUND
|
AI agent not found | Guardian has no record of the AI agent. Check the --agent-id value. |
SYNC_NO_BUNDLE_AVAILABLE
|
No enforcement bundle available for this agent | The AI agent exists in Guardian, but Guardian hasn't compiled an enforcement bundle for it yet. Click Apply latest rules on the Contract tab of the AI Agent asset page, wait for the compilation to finish, and then run the command again. |
INVALID_CREDENTIALS
|
Not applicable | Your token is expired or invalid. If you use OAuth 2.0, run collibra login again. Otherwise, check your credentials. |
SYNC_ACCESS_DENIED
|
Access denied | Your token is valid, but it doesn't cover this Collibra environment. Check your credentials. |
SYNC_SIGNED_URL_FAILED
|
Failed to obtain bundle download URL | Guardian didn't return a signed URL to download the bundle from. Run the command again. If the error persists, contact Collibra support. |
SYNC_BUNDLE_DOWNLOAD_FAILED
|
Failed to download enforcement bundle | A network error occurred while downloading the bundle from object storage, or the storage returned an error, for example because the signed URL expired. Run the command again. |
SYNC_CHECKSUM_MISMATCH
|
Enforcement bundle integrity check failed | The SHA-256 hash of the downloaded ZIP file doesn't match the hash that Guardian reported, so the download may be corrupted. The CLI discards the ZIP file and doesn't write it to disk. Run the command again. |
SYNC_BUNDLE_WRITE_FAILED
|
Failed to write enforcement bundle to disk | The CLI couldn't write the ZIP file to the --output path, for example because the disk is full or you don't have permission. Check the path, the free space, and your permissions. |
SYNC_MANIFEST_READ_FAILED
|
Failed to read bundle sidecar manifest | The bundle.manifest.yaml file exists, but the CLI can't read or parse it, for example because it was edited and broken. Delete the manifest file and run the command again. |
SYNC_MANIFEST_WRITE_FAILED
|
Failed to update bundle sidecar manifest | The CLI downloaded and verified the bundle, but couldn't write bundle.manifest.yaml, for example because you don't have permission. Check the permissions of the folder, and run the command again. |
Errors of the run command
These errors can occur when you run a Python program with Guardian attached. In the table, <interpreter> stands for the interpreter exactly as you typed it, such as python or .venv/bin/python.
| Error code | Message | Cause and fix | Exit status |
|---|---|---|---|
GUARDIAN_PROGRAM_MISSING
|
The interpreter or the program to run is missing | Fewer than two arguments follow run. A common cause is a command that leaves out the interpreter, such as collibra ai-gov guardian run my-agent.py. Put the command that you normally run after run, starting with the interpreter, for example collibra ai-gov guardian run python my-agent.py. |
3 |
GUARDIAN_INTERPRETER_NOT_FOUND
|
Python interpreter not found | The interpreter isn't on the PATH, doesn't exist at the path that you gave, or isn't executable. Check the interpreter name or path. | 3 |
GUARDIAN_PYTHON_TOO_OLD
|
The Python interpreter is too old for the Collibra SDK | The interpreter is older than Python 3.12. Run the command again with a newer interpreter, such as the one in your project's virtual environment. The CLI checks the version before it checks the SDK, so an old interpreter is reported as too old even if the SDK is also missing. | 3 |
GUARDIAN_SDK_NOT_INSTALLED
|
The Collibra SDK is not installed for this interpreter | The interpreter is new enough, but it can't find the SDK or one of the packages that the SDK needs. Install the SDK into that interpreter: pip install "collibra-sdk[guardian-injection,guardian-langchain]" |
3 |
GUARDIAN_SDK_FAILED_TO_LOAD
|
The Collibra SDK is installed but did not load | The interpreter found the SDK, but importing it raised an error other than a missing package, for example because one of its packages is broken. The error from Python is shown on the Caused by line. | 3 |
GUARDIAN_INTERPRETER_START_FAILED
|
Failed to start the Python interpreter | The interpreter file exists and is executable, but the operating system can't start it, for example because the file isn't a program. Check that the file is a Python interpreter. | 1 |