Runtime

Runtime is the working setup behind a skill set.

It keeps shared defaults for language, location, speech, blocked skills, and skill health.

Most users don’t need runtime on day one. Start with the default. Change runtime only when one hub needs different behavior.

Use Runtime When

• the wrong language appears;
• the wrong location or time zone affects a hub;
• a wrong timezone value appears in a client response;
• the wrong voice appears;
• a skill is unexpectedly blocked;
• a runtime or skill update is waiting.

What Runtime Means

Runtime is the set of shared working settings behind a skill set: language, location, speech, blocked skills, live skill status, update state. Every hub using that skill set gets them. Standard hubs share a runtime; Autoscaling hubs run their own workers, and you choose capacity on the hub. Leave the default alone until you’ve a reason. When you do, change it in Runtime config for that skill set.

Runtime config sits beside the store, behind the Runtime config button: the skill set’s shared language, location, speech and safety defaults.

Runtime Is Not a Hub

Runtime

Shared defaults for a skill set.

Skill set

The collection of skills a hub can use.

Hub

The place clients connect to.

Client

The app, device, or agent that connects.

What Runtime Controls

Runtime settings choose how your skills behave. To change capacity, choose Standard or Autoscaling on the hub. Billing shows the capacity available on your plan.

Runtime controls:

• primary language;
• secondary languages;
• location and time zone;
• speech-to-text and text-to-speech defaults;
• blocked skills;
• skill and runtime update state.

Default vs Separate Setup

Most workspaces start with workspace default skills. This keeps many hubs on the same simple setup.

Use a separate skill set when one hub needs different skills, different runtime settings, or a slower update pace.

Choice	Best when	What to remember
Workspace default	Most hubs should behave the same way.	Changing it can affect every hub using it.
Separate skill set	One hub needs different skills or settings.	Changes stay limited to hubs assigned to that skill set.

When to Open Runtime Config

Open runtime config when you need to:

• change the main language for a hub group;
• add secondary languages for a multilingual audience;
• set the location used by skills;
• choose speech-to-text or text-to-speech defaults;
• block a skill from loading in that skill set;
• understand why a runtime refresh is needed.

Tip

If only one skill needs to change, stay on the Skills page. Use runtime when the whole skill set needs shared defaults.

Runtime Is Ready When

Runtime is ready when:

• the selected skill set is the one used by the intended hub;
• shared defaults match the audience and location;
• secondary languages don’t duplicate the primary language;
• blocked skills match the safety goal;
• live skill status has no unexpected warning;
• Dashboard and Topology return to the expected state after any restart.