Deployment Problems

Overview

Deploying assistant updates—such as prompt revisions, avatar swaps, or knowledge collection links—takes effect across global edge nodes in under 15 seconds.

Changes Not Appearing Live (Stale Cache)

If changes made in the dashboard do not reflect on your production website:

1. Click Publish: Edits in the dashboard remain in draft mode until you click Publish Changes in the top navigation bar.

1. Browser Local Storage: The SDK caches active session parameters for up to 5 minutes. Clear local storage or test in a private browsing window.

1. Hard Refresh: Press Ctrl+Shift+R (or Cmd+Shift+R on macOS) to bypass intermediate browser caches.

Environment Promotion Mismatches

When promoting configuration from Development to Production:

1. Confirm that your production website uses your production public key (pk_live_...), not your development test key (pk_test_...).

1. Verify that your production domain is added to Allowed Domains in the Production environment tab.

CLI Deployment Failures

When deploying via CLI:

asiyst deploy --env production

If the command fails:

1. Run asiyst validate to check for syntax errors in your local asiyst.config.json.

1. Check that your ASIYST_API_TOKEN possesses administrative write permissions for the project.

Zero-Downtime Deployment Checklist