Deployment Troubleshooting

Activation Token Lifecycle Guide

This guide explains the Activation Token used during BitThor’s deployment finalization sequence, including how it works, why it expires, and the exact steps to resolve the two most common token-related deployment failures.

Overview
What Is the Activation Token?

The Activation Token is a short-lived credential issued by the BitThor server after your bot configuration passes the deployment hash check and connection health verification. It confirms that the configuration you simulated is the same configuration that will go live. The token has a strict 5-minute time-to-live (TTL) window. Once issued, you must complete the final activation step within that window. If the window elapses, the token expires and a fresh verification sequence is required. This mechanism exists to prevent deploying a configuration that may have drifted since the last verification.

TOKEN_EXPIRED
TOKEN_EXPIRED

This error means the 5-minute activation window elapsed before the final deployment step was completed. Common causes include navigating away from the deployment page, switching browser tabs for an extended period, or network delays during the health check stage.

  1. Return to the deployment finalization panel on the Dashboard page.
  2. Click the “Retry verification” button to initiate a fresh deployment confirmation sequence. This will re-validate your configuration hash, re-check the market connection, and issue a new 5-minute activation token.
  3. Complete the final activation step within the new 5-minute window without navigating away from the page.
CREDENTIAL_MISMATCH
CREDENTIAL_MISMATCH

This error means the bot’s saved configuration has changed since the simulation was run. BitThor computes a SHA-256 hash of the bot’s parameters at simulation time and again at deployment time. If the hashes do not match, deployment is blocked to prevent activating an untested configuration.

  1. Identify what changed: review your bot’s parameters (Buy Factor, Sell Factor, indicators, risk controls) to determine which settings were modified after the simulation.
  2. Re-run the simulation with the current bot configuration. This produces a new audit trail and a new configuration hash that matches the live bot.
  3. After the simulation completes successfully, proceed through the deployment gates again. The configuration hash will now match.
Quick Reference
Quick Reference: TOKEN_EXPIRED vs CREDENTIAL_MISMATCH
TOKEN_EXPIRED CREDENTIAL_MISMATCH
Cause The 5-minute activation window elapsed before the final deployment step. Bot parameters were modified after the last successful simulation.
Symptom Deployment blocked after a delay; token is no longer valid. Deployment blocked immediately; configuration hash does not match.
Fix Click “Retry verification” to issue a new token and complete activation within 5 minutes. Re-run the simulation with current settings, then re-attempt deployment.