Maintenance

Learn more about managing per-tenant quotas for Communications Mining™, and the model version deprecation process.

Quotas

All users can view quotas, but you need Tenant Admin permission to request changes to quotas.

The Quotas page allows users to view and manage quotas that are enforced for Communications Mining™ in the current tenant. Users with the Tenant Admin permission are able to easily request increases or decreases to each quota. For certain quotas, users will also be notified via Notification Service that they are approaching the limit and should request an increase.

To change the view of the Quotas in Current Tenant table, select the ellipsis menu from each column header:

A pop-up is displayed, where you can sort the columns in ascending or descending order, pin them to the left or right, filter (by columns, operator and value), hide or manage the items.

Example on how to change the limit for quotas:

1. Select the Edit Sources quota limit icon from the cells in the end column of the table.
   
   

   

   
   
2. A pop-up is displayed where you can set the new limit, from the up and down arrows.
   
   

   

   
   
3. Select the Update button to save the changes or Cancel, to close the pop-up, without applying any changes.

Note: If your limit request is too high, an error message is displayed. For a further increase, contact your Account Manager.

Deprecated models

User permissions required: Tenant Admin.

The Deprecated Models page shows you any model versions for datasets in your tenant that will soon be deprecated. All the production datasets are using more recent, improved model versions.

Note:

Having an empty page is expected, because it means that no model is going to be deprecated soon.

Notice on model deprecation and update requirements

To ensure optimal functionality and security, older pinned model versions (which will be at least 12 months old) may be scheduled for deprecation.

Deprecation announcement

To ensure a smooth transition, all deprecated models are flagged well in advance. You can find early deprecation indicators both within this page and in the Models page of the relevant dataset. This proactive approach gives you sufficient time to adjust your work without disruption.

Transition period

Following the initial announcement, you have a transition period of no less than three months. After this period ends, deprecated versions will be deemed unsupported. Consequently, unsupported versions will not be accessible via the API.

Unpinning deprecated models

You have to unpin deprecated model versions after pinning a more recent model version within the same dataset. This ensures the smooth continuation of service and API calls during the transition.

Updating production automations

You should immediately update the production automations that utilized the deprecated models, to a more recent model version. These changes prevent any potential interaction with deprecated models.