Uredi

Deli z drugimi prek

Orchestration workflow limits

  • Članek

Use this article to learn about the data and service limits when using orchestration workflow.

Language resource limits

  • Your Language resource has to be created in one of the supported regions.

  • Pricing tiers

    Tier Description Limit
    F0 Free tier You are only allowed one Language resource with the F0 tier per subscription.
    S Paid tier You can have up to 100 Language resources in the S tier per region.

See pricing for more information.

  • You can have up to 500 projects per resource.

  • Project names have to be unique within the same resource across all custom features.

Regional availability

See Language service regional availability.

API limits

Item Request type Maximum limit
Authoring API POST 10 per minute
Authoring API GET 100 per minute
Prediction API GET/POST 1,000 per minute

Quota limits

Pricing tier Item Limit
F Training time 1 hour per month
S Training time Unlimited, Pay as you go
F Prediction Calls 5,000 request per month
S Prediction Calls Unlimited, Pay as you go

Data limits

The following limits are observed for orchestration workflow.

Item Lower Limit Upper Limit
Count of utterances per project 1 15,000
Utterance length in characters 1 500
Count of intents per project 1 500
Count of trained models per project 0 10
Count of deployments per project 0 10

Naming limits

Attribute Limits
Project name You can only use letters (a-z, A-Z), and numbers (0-9) , symbols _ . -, with no spaces. Maximum allowed length is 50 characters.
Model name You can only use letters (a-z, A-Z), numbers (0-9) and symbols _ . -. Maximum allowed length is 50 characters.
Deployment name You can only use letters (a-z, A-Z), numbers (0-9) and symbols _ . -. Maximum allowed length is 50 characters.
Intent name You can only use letters (a-z, A-Z), numbers (0-9) and all symbols except ":", $ & % * ( ) + ~ # / ?. Maximum allowed length is 50 characters.

Next steps