## TL;DR
Replace the expired credential and restart the client: Polyaxon rejected the credential as expired, so issue a fresh one for the user or service account, update where the run environment reads it, and retry the run submission. An expired credential fails every call identically. No run level change matters until the client presents a credential the server still accepts.

```text
Polyaxon run failed error "PolyaxonClientException: unauthorized token expired"
```

## Use this when
- The check or run fails with this symptom: a Polyaxon run fails with PolyaxonClientException unauthorized token expired.
- You are working on a Polyaxon client or pipeline submitting runs to a Polyaxon deployment and the failure repeats on the same data or configuration.
- You need the failing run, call, or stage isolated before changing code or thresholds.

## Not for this skill when
- A credential that is valid but lacks permission for the project, which returns a forbidden response with a different message.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Confirm the failure time against the credential expiry shown in the Polyaxon settings. Verify: the credential used by the run is past its expiry
2. Generate a new credential for the account the runs use. Verify: a fresh credential exists
3. Update the secret or configuration the run environment reads it from. Verify: the client picks up the new credential on its next start
4. Run a lightweight client command, such as listing projects. Verify: the command succeeds with the new credential
5. Resubmit the failed run. Verify: the run is accepted and starts

## Variant phrasings
### polyaxon unauthorized token expired PolyaxonClientException
The shorter phrasing focused on the named failure.
### polyaxon run failed token expired error
The symptom phrasing a searcher tries next.
### polyaxon expired credential fix
The variant naming the failing stage or tool directly.

Compatibility: Polyaxon client and API credentials, Polyaxon Cloud and self-hosted deployments

## Why it happens
Polyaxon credentials carry lifetimes, and long lived run environments, CI jobs, and scheduled pipelines keep presenting the same credential after it lapses. The server reports expiry plainly, but the failure often surfaces deep inside a run submission where it reads like a run error.

## Edge cases / pitfalls
- Service accounts for automation should own the credential so a person leaving does not expire the pipeline.
- Store the credential in the platform secret store with a rotation reminder before its expiry date, not after a failed run.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_sztY-PQK27GpA2wUpvYNxg