Connection or setup is pending
Check your client's Atlas MCP status. Keep the browser authorization flow open while completing email verification, workspace setup, and deployment approval. A configured URL alone does not grant access.
If tools are missing after a server update, refresh the Atlas tool list or reconnect once while preserving saved credentials and other servers. If access is already valid, do not create another dashboard sign-in just to read project data.
Source upload did not finish
Check the returned upload method, headers, expiry, exact byte length, and SHA-256 digest. Do not change the archive after preparing it. Retry an uncertain PUT with the same upload ID; after success or a repeated PUT returning 412, call atlas_finish_deployment for validation.
When Atlas reports an expired upload, prepare a new upload with a new request ID and the same verified project ID. For archive validation errors, correct the exact path, file type, or size issue, then upload clean source. Keep credentials and runtime data excluded.
The build failed
Call atlas_get_deployment_logs for the exact project and deployment. Fix the reported dependency, build command, build-root, or code error. Deploy corrected source to the existing project using the direct-source tools.
A redeploy of saved source does not include local edits. Use atlas_prepare_deployment and atlas_finish_deployment when source changes.
The live app fails
Open the affected application path and read atlas_get_runtime_logs. It queries recent retained application logs over a bounded 30-minute window. Read the returned availability and time range; new records may take a moment to appear. Retry after reproducing the failing request if necessary.
Empty or unavailable logs do not establish that the application is healthy. Check the actual HTTP response, database schema and connection, server environment, and file API integration. Keep tokens and personal data out of application logs.
An environment setting is not live
Use atlas_set_environment_variables with the exact owned project. Names can be checked with atlas_list_environment_variables; values stay write-only. Keep secrets out of browser-prefixed names.
Saving a variable is separate from deploying it. The tool normally queues a redeploy; poll its actual status and test the application. A saved result without a successful redeploy does not confirm that the live app has the new value.
Need help
Send the project ID, Atlas deployment ID, time of failure, and redacted error to hello@atlasos.one. Leave out secrets, signed upload URLs, and private file contents. For missing telemetry, include the metric's reported availability and period. Read how usage availability works.