Skip to main content
App configurations control behavior across all access methods, customize the Playground experience, and provide advanced options such as error handling.

​
General Settings

General settings apply across all access methods: Public APIs, Playground, and SDK.

​
Attachment Configuration

Controls file upload behavior when users share documents during interactions. Click Modify Configuration to set the following: See Attachment Support in User Interactions.

​
Thought Streaming

Allows you to customize the prompt used for thought streaming. Click Modify Prompt and enter the prompt for the LLM.

​
Waiting Experience

Configures user engagement during processing delays in voice interactions. When enabled, filler messages play automatically while the system processes a response and stop when output is ready.
This feature only works in ASR/TTS streaming mode. Real-time models are not supported.
Click Modify Configuration to set the following: Dynamic Messages configuration:

​
Playground Settings

The following settings apply only to the Playground.

​
Microsoft Agent 365

Enable Microsoft Agent 365 integration for the agentic app. When enabled, the platform automatically creates the required Agent 365 environment variables required to connect the app to a Microsoft 365 tenant and authenticate the integration. The following variables are automatically created in Settings > Variables:
  • A365 Blueprint ID
  • A365 Tenant ID
  • A365 Client Secret Ref
After enabling the integration, complete the Microsoft Agent 365 onboarding and setup process described in the Microsoft Agent 365 Integration Guide.

​
Advanced Settings

​
Error Handling

Agent Platform provides an error-handling framework that defines how the system responds when an agent’s underlying AI model requests fail or guardrail violations occur. Administrators can configure timeouts, retries, fallback models, and fallback behaviors to ensure predictable and graceful user experiences even when model calls fail or are delayed.
All agents within the app inherit these configurations.

​
Model Errors

These configurations apply to agent model invocation failures such as timeouts, provider errors, or transient network issues. Model Call Timeout Defines the maximum time (in seconds) the system waits for a model response before marking the call as failed. If the model does not respond within the configured timeout, the call is treated as failed and the retry mechanism is triggered. Retry Handling Defines how the system behaves when a model call times out. Two options are available: Fallback Behavior Defines what happens when the model request fails after all retry attempts have been exhausted. Fallback Action Specifies whether the system should trigger an automated recovery step. Available actions:
  • None — No automated action is taken.
  • Invoke an event — Executes a configured event. Options: Agent Handoff or the End of Conversation event.
  • Invoke a tool — Executes a selected code tool or workflow tool. Provide the tool parameters using either fixed key–value pairs or memory variables for dynamic runtime values.
Common use cases for invoking a tool:
  • Triggering a notification or email
  • Logging failure details
  • Initiating a fallback recovery workflow
  • Informing support systems when repeated model calls fail
Fallback Message Controls the message shown to end users when all retry attempts fail:
  • Send Message — Displays a custom message describing the issue and next steps.
  • Do not send a message — No message is shown.

​
Guardrail Errors

Use this section to configure handling for guardrail violations such as safety, policy, or validation failures. These settings define how the system behaves when a guardrail check fails, times out, or detects a policy breach.
Key points:
  • Guardrail failure and guardrail breach are handled separately.
  • Retry settings apply only to guardrail call failures, not breaches.
  • Fallback actions run after retries are exhausted.
Guardrail handling is evaluated in two scenarios:
  1. The guardrail call fails or times out
  2. The guardrail detects a policy breach

​
If Guardrail Call Fails

Timeout Configuration Specifies how long (in seconds) the system waits for the guardrail response before marking the call as failed. If the guardrail responds within this period, normal execution continues; otherwise, retry handling begins. Retry Handling Defines how the system retries when a guardrail call fails or times out. The system retries the guardrail call up to the configured count.
  • If a retry succeeds, normal flow resumes.
  • If all retries fail, fallback behavior executes.
Fallback Behavior Executed when the guardrail call fails after all retries. Fallback Action — Specifies the action to trigger, such as running a remediation workflow, logging an incident, or initiating an alert. Available actions:
  • None — No additional action is taken.
  • Invoke an event — Executes Agent Handoff or End of Conversation event.
  • Invoke a tool — Executes a configured tool. Assign static values to parameters or provide dynamic values using memory variables.
Fallback Message — Controls the message displayed to users after a guardrail call fails. A custom message can be configured.

​
If Guardrail Is Breached

Defines behavior when the guardrail successfully evaluates a request and detects a policy violation. Breach Handling Triggered when user input or model output violates configured safety or policy rules. Fallback Action — Specifies the automated step to execute when a breach is detected, such as compliance logging, security alerts, or running moderation workflows. Available actions:
  • None — No additional automation.
  • Invoke an event or tool — Executes a defined failure event or workflow tool.
Fallback Message — Defines the message shown to the user when a guardrail breach occurs.

​
Delete Agentic App

Permanently deletes the Agentic App and all associated data. This action cannot be undone.