FAQ and troubleshooting
Answers to common questions and fixes for issues you may run into across the Console, deployment, and Studio. If you don't find your answer here, contact your account team.
General
Where does my data live?
Everything you create in Studio — agents, conversations, documents, datasets, connector credentials, and knowledge graphs — stays inside your own AWS account (and your own knowledge-graph database). The only information that flows out is license and usage telemetry sent to the Console. See Data residency and security.
Does PrometheusRL ever see my data?
No. The Console is a management portal and never connects to your AWS account. It receives only signed license activation, heartbeat, and usage information. See Licensing and telemetry.
What is the difference between the Console and Studio?
The Console is the hosted portal for account, billing, licensing, and downloads. Studio is the product you deploy into your AWS account and work in. See What is AlphaAgent?.
Which AWS regions and residency zones are supported?
Model inference runs on AWS Bedrock pinned to a single residency zone — United States or European Union — that you choose at deploy time. Inference never crosses zones. See Data residency and security.
Account and licensing
I lost my license token. What do I do?
The license token (the aalk_<id>.<secret> value) is shown only once when you create the key. If you lost it before deploying, create a new license key and use its token. The public license id is always visible in the Console. See License keys.
My Studio shows a license warning banner. What does it mean?
Studio periodically checks in with the Console via a heartbeat. If those check-ins cannot complete — for example because of a billing issue or a network problem reaching the Console — Studio shows a warning banner. If the problem is not resolved, execution may eventually be blocked. Check your subscription status in the Console and confirm Studio can reach the Console. See Licensing and telemetry.
Will a temporary Console outage stop my work?
No. Studio is designed to keep working through brief interruptions and to deliver usage information reliably once the Console is reachable again. Only a sustained, unresolved licensing problem blocks execution.
Deployment
Where do I get the install bundle?
Download it from the Console's download page after creating a license key. See Downloading Studio.
The pre-deployment checks failed. What should I look at?
The installer runs preflight checks before making changes. Common causes are missing AWS permissions, an unverified domain or certificate, model access not yet granted in Bedrock, or your identity provider details not being ready. Review the Prerequisites and the Deployment troubleshooting guide.
How do I update Studio to a new version?
Download the new bundle from the Console and run studioctl update. By default it auto-detects whether the release is a code-only change or also changes infrastructure; you can force either with --image-only or --infra. Infrastructure changes are shown as a reviewed change set and any destructive change requires confirmation. See Updating Studio.
How do I remove Studio?
Use the teardown process, which removes the resources the installer created. Some data stores may be retained by design so you don't lose data accidentally. See Teardown.
Sign-in and access
How do users sign in to Studio?
Studio uses single sign-on through your own identity provider (SAML). There is no separate username and password to manage in Studio. See Single sign-on (SAML).
Why can't I see another user's agents or conversations?
Resources are owned by the user who created them. Each user sees their own agents, conversations, datasets, and other resources. This isolation is by design. See Data residency and security.
Building agents
I edited my agent but chat still behaves the old way. Why?
Editing an agent creates a new version but does not change what is live. Activate the new version so it becomes the active configuration. See Agents.
Why can't I deactivate an agent?
If the agent is used as a supervisor or specialist in an active swarm, AlphaAgent prevents deactivation so the swarm doesn't break. Remove it from the swarm or deactivate the swarm first. See Swarms.
Why won't my swarm activate?
A swarm can only be activated when all of its member agents have an active configuration. Activate the members first. See Swarms.
I updated a knowledge graph and some agents stopped using it. What happened?
A knowledge graph keeps a single live version. When you re-ingest, AlphaAgent guides you through an impact and reactivation flow for the agents and swarms that depend on it. See Knowledge Graphs (AMPG).
Chat and data
When should I use Express versus Deep Traversal?
Use Express for quick, direct questions and short tasks. Use Deep Traversal for complex questions that benefit from planning and knowledge-graph retrieval, and when you want to review a plan before the agent proceeds. See Chat.
My results table isn't showing every row in the chat. Is that a bug?
No. Large result tables are registered as datasets and shown as compact previews, charts, or grids so the conversation stays readable. The full data remains in your workspace. See Datasets and data flow.
How long do datasets last?
Session datasets are retained for 6 hours. See Limits and quotas.
My document upload was rejected. Why?
Check the file type and size against the Limits and quotas. Knowledge-graph documents are limited to 100 pages and 50 MiB; chat attachments are limited to 4.5 MB per file and specific file types.
Workflows
Why can't I add more nodes to my workflow?
A workflow can contain up to 12 nodes. See Limits and quotas. Consider splitting a large process into multiple workflows.
How do I schedule a workflow?
Describe the schedule in plain language (for example, "every weekday at 8am") and AlphaAgent translates it into a recurring schedule. See Workflows.
Can a later workflow step use data produced by an earlier step?
Yes. A step can load a dataset produced by an upstream step, even though each step runs in its own workspace. See Datasets and data flow.