Terminology
We use these terms to describe the status of a feature or functionality:- Deprecated: We no longer actively develop a feature or functionality and will remove it in a future release.
- End of support: We no longer offer support and servicing for a product.
- Retired: We remove a feature or functionality after it has been deprecated. It’s no longer available for use.
- Replace a feature: We replace a feature or functionality with a different feature or functionality.
Deprecated and retired features and functionality
| Feature | Deprecated date | Retired date | Details and mitigations (actions required by you) |
|---|---|---|---|
totalVariation aggregate for numeric time series | 2026-04-20 | 2027-04-20 | We’re deprecating the totalVariation aggregate for numeric time series on the time series data list endpoint (/timeseries/data/list). During the deprecation period, the aggregate continues to work as documented. After the retirement date, requests that include totalVariation return an error. Action required: If your integrations use totalVariation through the API, an SDK, dashboards, or derived pipelines, review them before April 20, 2027 and migrate to another aggregate or compute the value client-side from raw data points. If no alternative fits your workflow, contact your Cognite representative with your use case, time series volume and aggregation granularity, and whether client-side computation is feasible. |
| Vision API | 2026-02-17 | 2027-02-17 | We’re deprecating all endpoints under the Cognite Vision API, including text detection, asset tag detection, human detection, PPE detection, industrial object detection, and gauge reading. The API remains operational during the deprecation period but will not receive new features. Action required: If you call the Vision API directly, migrate custom scripts or integrations before the retirement date. For text and tag detection, use the Detect annotations in engineering diagrams endpoint or a managed OCR service. For gauges, valves, and PPE detection, use a dedicated computer vision platform or custom models. If you use 3D 360-image contextualization, no action is required — the backend transition is handled automatically. |
| Image and video management | 2026-02-17 | 2027-02-17 | We’re deprecating Image and video management in the Data fusion workspace > Contextualize > Images and videos, including the map view, annotation tool, and video streaming and viewing. Your image and video files stored in Cognite Data Fusion (CDF) are not affected and remain accessible through the Cognite API and Data explorer. During the deprecation period, we’ll be working on image and video workflow support in core tools such as Data explorer and Canvas. Action required: You can continue to use the interface during the deprecation period. After retirement, access your files through Data explorer or the Cognite API or the Cognite SDK. If you depend on this interface, contact your representative. |
CDF CLI package (@cognite/cdf-cli) | 2025-12-18 | 2026-02-18 | The @cognite/cdf-cli package will be unpublished from npm on February 18, 2026. Action required: Remove @cognite/cdf-cli from your CI/CD pipelines and local development environments before February 18, 2026, to avoid build failures. |
| Set threshold rules in Canvas | N/A | N/A | Starting January 1, 2026, we are moving the Set threshold rules feature from public preview to private preview. The change will not affect existing users who have previously enabled and are using the feature daily. No actions necessary. |
| Current backend for Cognite Functions on Azure | 2025-12-02 | 2026-12-02 | We’re deprecating the current backend for Cognite Functions on Azure. A new backend is now in production and all functions deployed from now onwards will automatically use the new backend. Action required: Existing functions will continue to run on the current backend, but to benefit from improved performance and future updates, you need to redeploy your functions. We will not automatically migrate existing functions. |
| AI integration in Jupyter Notebook | October, 2025 | December, 2025 | As of early December 2025, we will no longer support AI features in Jupyter Notebook for generating code snippets and modifying existing code through natural language queries. No actions necessary. |
| InRobot | December, 2025 | January, 2026 | Starting at the end of December 2025, we’ll no longer be developing new features or providing support for InRobot. However, you can still access the data in your project in CDF and the Robotics API after retirement. No actions necessary. |
| Python 3.10 in Cognite Functions | 2025-10-01 | 2026-10-01 | Update the Python runtime to version 3.11 or later to continue using Cognite Functions. |
| Data profiling in Charts | 2025-08-11 | 2026-08-11 | Starting August 11, 2025, we’ll no longer be updating and supporting the Data profiling functionality in Charts. No actions necessary. |
| Power BI OData connector | 2025-08-18 | 2026-08-18 | The Power BI OData connector is deprecated in favor of the Power BI REST API connector. Migrate existing reports to the REST API connector before the retirement date. |
| Navigate categories and filters using AI in search | 2025-04-04 | 2025-06-04 | No actions necessary. |
| Features in the Data modeling user interface | 2025-04-03 | 2025-06-03 | Applies to Population, Smart suggestions, and Knowledge graph. |
Templates API /templates (Beta) | 2025-03-01 | 2025-05-31 | Migrate to the Data Modeling Service (DMS). |
| The assetIds, labels and geoLocation fields in the Documents API | 2025-02-01 | 2026-02-01 | Use the sourceFile.assetIds, sourceFile.labels and sourceFile.geoLocation fields instead. |
| Python 3.9 in Cognite Functions | 2024-10-01 | 2025-10-01 | Update the Python runtime to version 3.10 or later to continue using Cognite Functions. |
| Transformations CLI | 2024-10-01 | 2025-10-01 | CDF Toolkit replaces Transformations CLI. |
| Maintain v1 | 2024-08-06 | 2025-08-06 | Maintain v2 replaces Maintain v1. |
| Runtime for Cognite Functions on Google Cloud | 2024-04-23 | 2025-04-23 | A new runtime for Cognite Functions has been rolled out. Functions created before March 22, 2024 on a Google Cloud cluster will need to be re-created to continue using Cognite Functions. |