aireg loads the Atlan adapter but an Atlan workflow fails.
For generic CLI errors, use the aireg CLI reference.
Adapter is missing or cannot install
Runaireg adapter list. If atlan is missing, run
aireg adapter install atlan. A source build without a signed release origin
cannot install the adapter; use the released CLI. Check the CLI version with
aireg --version separately from the adapter version.
Sign-in fails
An HTTP 401 means the credential was rejected. Sign in again through the browser or with a current user token. Do not add a token to a command argument or share an unredacted log.aireg auth login exits with status 4 when the browser sign-in is declined,
refused, or not finished within five minutes. Run it again. If it says it
needs a token for this registry, the registry’s address has no browser
sign-in: browser sign-in is available for https://api.atlan.com and
https://api.atlan.dev with aireg 0.1.9 or later. For another address, pipe a
user token with --token-stdin.
The account you signed in with cannot use <org>. means the account isn’t
allowed in the organization the registry’s organisation setting names. Sign
in with an account in that organization, or check the setting.
Atlan sign-in is for <org>, but this registry is for <other-org>. means the stored
browser sign-in was issued for a different organization than the registry
declares. Run aireg auth login <registry> again.
An HTTP 403 can mean the identity lacks membership or permission for the
operation. Check your organization and workspace access with an administrator.
A service account API key does not perform user onboarding; use
AIREG_TOKEN_<NAME> for CI publishing.
If AIREG_TOKEN_<NAME> is set, it takes precedence over a stored account and
prevents aireg auth login from storing another credential for that name.
Unset it before an interactive login.
Session expires
A browser sign-in renews itself. When it can no longer renew, the CLI reportsThe sign-in to <org> has ended. Run aireg auth login <registry> again.
The Atlan adapter can refresh a piped user token only when the corresponding
organization’s Atlan Trident Desktop session is available locally. Sign back in to
Desktop if that session has expired or been revoked. On a machine with only a
copied bearer token, obtain a current token or sign in through the browser. A
per-run token variable does not create a refresh session for a background job.
Registry address is rejected
Use the Gateway origin, such ashttps://api.atlan.com, with no path, query,
fragment, or embedded credentials. The Atlan adapter accepts HTTPS on Atlan
domains only. --address is the current login option; the earlier --source
spelling is not an aireg option.
If the adapter rejects a configuration key, check against
Registry settings.
Only organisation, default_namespace, and channel are accepted.
A pinned version fails to install
Atlan serves <name> <release> now, not <version>: a registry keeps one release per artifact. means the pin names a version the channel no longer serves. Run
aireg update <name> to move to the release the message names, or remove
@<version> from the address and let the channel setting choose the release.
Workspace skills missing from the catalog
The Atlan adapter leaves a workspace with more than 50 skills out of the catalog, and reports no error when it does. None of that workspace’s skills appear when you list or sync the whole registry, and the next sync oraireg update removes copies installed from it; a copy you edited locally is
kept as a conflict. A skill you name still installs and stays, for example
aireg add atlan/<workspace>/skill/<name>. Skills awaiting review count toward
the cap; archived and scan-blocked skills do not. Archiving skills the
workspace does not need brings it back under the cap and restores its skills
to the catalog.
Publish held or blocked
A stored version can wait for scanning or approval before it becomes installable. Open the skill in Atlan Trident and inspect that version’s review state. A blocked security scan requires fixing the reported content and publishing a new version. Repeating installation does not bypass review. The adapter publishes skills and agents. For other resource types, use the SDK or API. You cannot overwrite skills shipped in theatlanai namespace.
If a publish is refused because no workspace you can reach has the requested
name, check aireg registry show <registry> and preview again with --dry-run
before publishing. A misspelled or inaccessible workspace name is refused
rather than published to the account’s default workspace.
Publish refused because the skill already exists
<name> already exists in this workspace, published from another repository, so <path> was not published. Rename one of them to publish both.
The workspace already holds a skill of that name from another source: another
repository, or a Git repository Atlan Trident does not name. aireg does not take over
a skill another source owns. Rename the skill in your checkout, or publish it to
a different workspace. A skill created in Atlan Trident is not refused: aireg adopts
it and keeps its history.
Traces missing in Atlan Trident
- Confirm the account using
aireg auth listand supply that name with--account. A token variable alone is insufficient. - Run
aireg trace listand check that the session exists locally. - Export the session manually. Unfinished work can remain local until it is finalized.
- Check the personal workspace or configured
default_namespacein Atlan Trident. - For a job, inspect
aireg job listandaireg job runs, then confirm the background service is running.
--content drop or
organization policy removes content. Do not change organization policy to
diagnose missing spans; first verify the session and trace destination.
Previous collector still runs
Check whether Atlan Trident Desktop managesbrain, or an old atlanai plugin,
hook, or background service remains installed. Use the application’s upgrade
and deployment process to retire the old collector after the replacement is
verified. See Move to aireg.