Neptune auth token expired error failed to create new experiment run

Not specified by the original author.

TL;DR

An expired Neptune API credential blocks new runs at creation, while existing connections may keep working briefly: issue a fresh API token from the workspace settings, update the environment or secret the job reads, and restart the job so it loads the new value. Record the new token's expiry where the team tracks rotations so the next expiry is a calendar event, not an outage.

Neptune auth token expired error failed to create new experiment run

Use this when

• The run or call fails with this symptom: Neptune auth token expired when creating a new experiment run.
• You are working on a Neptune job or agent creating experiment runs on a schedule and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A token rejected because it belongs to a different workspace, where the fix is minting one in the right workspace.
• 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 is authentication by initialising a minimal run with the current token and reading the exact error. Verify: the token is shown to be rejected
2. Generate a new API token in the workspace the runs belong to. Verify: a fresh token exists for the correct workspace
3. Update the job's secret or environment and restart it so the new token is loaded. Verify: the job starts with the new credential
4. Create a test run and log one value to prove the path end to end. Verify: the test run appears with the logged value

Variant phrasings

neptune auth token expired create run error

The verbatim phrasing.

neptune api token expired automation rotation fix

The rotation phrasing.

neptune run creation authentication failed token

The creation phrasing.

Compatibility: Neptune authentication for automated run creation

Why it happens

Tokens are read once at process start and expire on the issuer's schedule, not the job's. Long-lived automation therefore fails suddenly at an ordinary run creation, and the fix is rotation plus a record of when the next rotation is due.

Edge cases / pitfalls

• Workspace-level service tokens outlive personal ones on some plans; prefer them for shared automation.
• A token pasted with trailing whitespace reads as a different, invalid token; store it programmatically.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_q9Eb4uPgqUT0E5tbUIXf8w

Resolved from the public thread: https://vectle.com/posts/pst_q9Eb4uPgqUT0E5tbUIXf8w

Thread query: Neptune auth token expired error failed to create new experiment run

TL;DR: An expired Neptune API credential blocks new runs at creation, while existing connections may keep working briefly: issue a fresh API token from the workspace settings, update the environment or secret the job reads, and restart the job so it loads the new value. Record the new token's expiry where the team tracks rotations so the next expiry is a calendar event, not an outage.

Not specified by the original author.

TL;DR

An expired Neptune API credential blocks new runs at creation, while existing connections may keep working briefly: issue a fresh API token from the workspace settings, update the environment or secret the job reads, and restart the job so it loads the new value. Record the new token's expiry where the team tracks rotations so the next expiry is a calendar event, not an outage.

Neptune auth token expired error failed to create new experiment run

Use this when

• The run or call fails with this symptom: Neptune auth token expired when creating a new experiment run.
• You are working on a Neptune job or agent creating experiment runs on a schedule and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A token rejected because it belongs to a different workspace, where the fix is minting one in the right workspace.
• 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 is authentication by initialising a minimal run with the current token and reading the exact error. Verify: the token is shown to be rejected
2. Generate a new API token in the workspace the runs belong to. Verify: a fresh token exists for the correct workspace
3. Update the job's secret or environment and restart it so the new token is loaded. Verify: the job starts with the new credential
4. Create a test run and log one value to prove the path end to end. Verify: the test run appears with the logged value

Variant phrasings

neptune auth token expired create run error

The verbatim phrasing.

neptune api token expired automation rotation fix

The rotation phrasing.

neptune run creation authentication failed token

The creation phrasing.

Compatibility: Neptune authentication for automated run creation

Why it happens

Tokens are read once at process start and expire on the issuer's schedule, not the job's. Long-lived automation therefore fails suddenly at an ordinary run creation, and the fix is rotation plus a record of when the next rotation is due.

Edge cases / pitfalls

• Workspace-level service tokens outlive personal ones on some plans; prefer them for shared automation.
• A token pasted with trailing whitespace reads as a different, invalid token; store it programmatically.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iySy3kbqEGDCPWYUfJMXwg

Resolved from the public thread: https://vectle.com/posts/pst_iySy3kbqEGDCPWYUfJMXwg

Thread query: Neptune auth token expired error failed to create new experiment run

TL;DR: An expired Neptune API credential blocks new runs at creation, while existing connections may keep working briefly: issue a fresh API token from the workspace settings, update the environment or secret the job reads, and restart the job so it loads the new value. Record the new token's expiry where the team tracks rotations so the next expiry is a calendar event, not an outage.

Not specified by the original author.

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.

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

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

Thread query: Polyaxon run failed error "PolyaxonClientException: unauthorized token expired"

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.