October 2026 Release
October 2026 expands what teams can configure in Studio flows and makes peer chat behavior easier to understand when safety rules block a message. Teams upgrading must run the database migration before starting this version, then review any flow sandbox steps that should use the new CPU, memory, or disk settings.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- Speech to Text now supports Azure transcription models and returns richer transcript output in flows.
- Flow sandbox steps now accept CPU, memory, and disk sizing inputs for heavier workloads.
- Sandbox failures now return clearer details, which makes failed flow runs easier to diagnose.
- Peer chats now show clearer blocked-message notices and no longer expose raw provider errors.
New in Studio
- In the Speech to Text step, teams can choose from Azure transcription models instead of relying on a single fixed option.
- Flow transcripts now include richer output, which helps downstream flow steps work with more detailed transcription results.
- Sandbox: Create steps now let builders request CPU, memory, and disk resources directly in the flow configuration.
- When a sandbox execution fails, Studio now shows clearer failure details to help teams understand what went wrong.
- Peer previews behave more reliably, and blocked messages are explained more clearly in chat.
For organization admins
- Run the database migration before starting this release.
- After upgrading, review any flows that create sandboxes and decide whether they should use the new CPU, memory, or disk settings.
- If your teams rely on peer chat moderation, expect clearer blocked-message notices and less exposure to low-level provider error text.
For developers
- Re-test flows that use Speech to Text and confirm the selected Azure transcription model and transcript output match your expected downstream behavior.
- Re-test sandbox-based flows after the migration, especially where larger workloads may benefit from explicit CPU, memory, or disk sizing.
- Verify peer preview sessions and blocked-message handling in any custom peer experiences you maintain.
- Use the Developer Hub for technical implementation details and API guidance.
What to try
- Update a flow's Speech to Text step to use an Azure transcription model and inspect the richer transcript output it returns.
- Open a flow that creates a sandbox and review whether CPU, memory, or disk sizing should be configured for that workload.
- Trigger a sandbox failure in a test flow and confirm the returned details are easier to diagnose.
- Test a peer conversation that is blocked by guardrails and confirm the notice shown to users is clearer.
Action required
- Run the database migration before starting Studio v1.7.0.
- After the migration, review existing sandbox steps if you want to use the new CPU, memory, or disk configuration fields.