Documentation Login

Docs Home Resources

Stages Transitions Prompting Variables Integrations

Design Implementing Building, Editing & Debugging

General Reference

Prompt Sandwiching Prompt Formatting Reviewing Prompting

Defining Variables Updating Variable Values Revealing Variable Values

RAG and Content Retrieval External Service Integrations

Creating New Stages Editing Stages Editing Transitions

Debugging Snapshots

Settings Common Stage Settings Variables

Defining Integrations

Slack Webhook Make Webhook Zapier Webhook n8n Webhook

Custom Function Using a Custom Function Calling External Services AWS SigV4 Signing

Defining a Pinecone RAG Using a Pinecone RAG Definition

Defining a Weaviate RAG Using a Weaviate RAG Definition

Defining a Custom Content Retriever Using a Custom Content Retrieval Definition AWS Bedrock SigV4 Signing

Widget & Inference API Access

Versioning Environments Agent Access Keys Agent Reviews Deployed Agents

ReferenceAuthoring Portal ReferencePublishing

Deployed Agents

An Agent is considered as deployed if it has one or more Environments with an active Version.

Deployed Agent Limits

Your iostack plan comes with a limit restricting your account's total deployed agents.

Deploying new Agents if you reach the Deployed Agent Limit

If you run up against the deployed agent limit while publishing an Agent to an Environment:

Identify any unneeded Agents.
Then for each unneeded Agent, remove any active Versions from all Environments.
Retry publishing you Agent.

NB: Removing an active Version from an Environment will disable any access by clients using that Environment's access key or widget code.

Previous

Agent Reviews

Next

Account

On this page

Deployed Agent Limits Deploying new Agents if you reach the Deployed Agent Limit