Troubleshooting

Running into a problem? This page covers the most common issues users encounter with Straion. Jump to the relevant section:

Prerequisites

Access to one or more of these coding agents: Claude Code (minimum version 2.1.84), Cursor, or GitHub Copilot
A Straion account
MacOS/Windows and Node.js v22+
Sufficient permissions on your computer to install the Straion CLI

Check Agent Setup

Before connecting Straion, verify your coding agent CLI is installed. Run the command for your agent:

Agent	Check command	Supported version
Claude Code	`claude --version`	> 2.1.84
GitHub Copilot	`copilot --version`	> 1.0.0
Cursor	`agent --version`	> 3.0.0

If a command is not found, follow the install guide linked in the table above.

Firewall Issues

Some corporate or network firewalls may block outbound requests from the Straion CLI. If you’re seeing connection errors or timeouts, check with your network administrator to ensure that outbound HTTPS traffic to Straion’s services is allowed.

Permission Issues

Double-check your user token or generate a new one in the User Settings. The token inherits your permissions and can be scoped with an expiration date.

Common issues

Agent setup finished, but skills are not available

Try upgrading your agent if you have ran straion and performed the agent setup or ran straion setup, but the skills are not available inside your agent.

SAML SSO

Setup steps live on the SAML SSO page.

No SAML connection exists for that subdomain. Check the spelling (the subdomain is the slug in your workspace URL — acme for acme.straion.app) and confirm the connection exists on the Identity & provisioning page.

”User not part of organization”

SSO authenticated the user, but they aren’t a member of your Straion organization yet. Invite them or provision them via SCIM first. The email address in your IdP must match their Straion account email exactly.

”SAML connection could not be created / updated”

Straion couldn’t fetch or parse the metadata. Two common causes:

The metadata URL isn’t reachable from Straion’s servers (e.g. it requires an authenticated session). Download the XML and paste it instead — and clear the Metadata URL field, since a filled URL takes precedence over pasted XML.
The pasted XML is incomplete or was reformatted by an editor. Re-download the metadata from your IdP and paste it unmodified.

The assertion was rejected. Verify the Audience URI in your IdP exactly matches the value shown in Straion (including the scheme, no trailing slash) and that the NameID is the user’s email address.

SCIM provisioning

Setup steps live on the SCIM provisioning page.

The IdP’s connection test fails with 401 Unauthorized

The bearer token doesn’t match. Copy the SCIM Secret again (use the copy button — a revealed secret can be mis-selected) and make sure the authentication mode is HTTP Header / Bearer token. If the connection was deleted and recreated in Straion, the old secret is no longer valid.

”User already exists” when assigning someone

The user was already provisioned through this connection — usually after retrying a partially failed assignment. Unassign and re-assign them, or check whether they already appear in User Management.

A provisioned user can’t log in with SSO

SCIM and SSO match users by email address. Make sure the email your IdP sends via SCIM is the same one used as the SAML NameID (see SAML SSO).

Deprovisioned users still appear in User Management

They’re deactivated, not deleted — access is already revoked. The default member list hides them; enable the show deactivated toggle to see them.

Groups from my IdP aren’t showing up in Straion

Straion doesn’t sync groups yet. Assigning a group in your IdP provisions its members as individual users — the members get access, but the group itself isn’t created in Straion.

More Coming Soon

Troubleshooting content is on its way. If you’re running into an issue, reach out to support via email at support@straion.com or on Discord and we’ll help you get unblocked.