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
The rows dated 2026-10-15 announce the deprecation of asset-centric services. Full retirements take effect on December 31, 2027. Asset-centric time series and file metadata follow the same dates, while data point and file content operations remain available through
instanceId. Data modeling status for CDF projects describes how DATA_MODELING_ONLY and HYBRID projects behave while you upgrade.| Feature | Deprecated date | Retired date | Details and mitigations (actions required by you) |
|---|---|---|---|
| Asset-centric metadata and asset filters on the Files API | 2026-10-15 | 2027-12-31 | We’re deprecating asset-centric file metadata and the asset filters assetIds, assetExternalIds, rootAssetIds, assetSubtreeIds and assetSubtreeExternalIds on advanced list, aggregate, list, and search. Look up files by querying CogniteFile instances connected to CogniteAsset. Metadata updates for CogniteFile are blocked on the files update endpoint, and files cannot be linked to asset-centric assets. Data set and label governance on files is removed. File content upload and download stay on the Files API and use instanceId. The files upload (single-part and multi-part) endpoints stays available also for files that are not CogniteFile when you have the files:write capability. Action required: Create and query files as CogniteFile instances before December 31, 2027. You can upgrade files with the migration plugin. |
| Asset-centric metadata and asset filters on the Time series API | 2026-10-15 | 2027-12-31 | We’re deprecating asset-centric time series metadata and asset-hierarchy filters. Data point reads and writes stay on the Time series API and use instanceId. Action required: Create and query time series as CogniteTimeSeries instances before December 31, 2027. You can upgrade time series with the migration plugin. |
| Asset-centric support in the Engineering diagrams API | 2026-10-15 | 2027-12-31 | We’re deprecating asset-centric support in the diagram detect and convert endpoints (/context/diagram/detect and /context/diagram/convert). This covers referencing files by fileId or fileExternalId and the assetsAcl:READ requirement for retrieving results. The endpoints remain available and continue to support files in the core data model. Action required: Before December 31, 2027, reference files with fileInstanceId, pass entities from your data model, and store results in the core data model instead of with the Annotations API. See Diagram parsing for data modeling. |
| Annotations API | 2026-10-15 | 2027-12-31 | We’re deprecating the Annotations API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Move annotations to CogniteAnnotation in the core data model before December 31, 2027. You can upgrade annotations with the migration plugin. |
| Assets API | 2026-10-15 | 2027-12-31 | We’re deprecating the Assets API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Move asset hierarchies to CogniteAsset in the core data model before December 31, 2027. You can upgrade assets with the migration plugin. |
| Data sets API | 2026-10-15 | 2027-12-31 | We’re deprecating the Data sets API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Scope data with spaces and govern consumption with data products before December 31, 2027. You can upgrade data sets with the migration plugin. |
| Events API | 2026-10-15 | 2027-12-31 | We’re deprecating the Events API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Move high-volume alarms, logs, and notifications to records. Move workflow activities to CogniteActivity or CogniteMaintenanceOrder. Complete the move before December 31, 2027. You can upgrade events with the migration plugin. |
| Geospatial API | 2026-10-15 | 2027-12-31 | We’re deprecating the Geospatial API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: There is no replacement in the data modeling service. Plan to stop using the Geospatial API before December 31, 2027. |
| Labels API | 2026-10-15 | 2027-12-31 | We’re deprecating the Labels API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: There is no direct replacement. Model labels as a concept in your data model before December 31, 2027. |
| Relationships API | 2026-10-15 | 2027-12-31 | We’re deprecating the Relationships API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Model connections as edges or direct relations in the data modeling service before December 31, 2027. |
| Security categories API | 2026-10-15 | 2027-12-31 | We’re deprecating the Security categories API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: Replace security categories with data products and granular access control before December 31, 2027. |
| Sequences API | 2026-10-15 | 2027-12-31 | We’re deprecating the Sequences API. The API remains available during the deprecation period but will not receive new features. After the retirement date, the API shuts down. Action required: For tables that consumers download as a whole, use files in data modeling. For multi-column data that needs row-level queries, use records. Complete the move before December 31, 2027. |
| Asset-centric 3D contextualization | 2026-10-15 | N/A | We’re deprecating asset-centric 3D contextualization approvals using the CAD node 3D asset mapping endpoints and the Annotations API used for the pointcloud.BoundingVolume and images.assetLink/instanceLink (360-images). Action required: Contextualize 3D models in a data modeling project with the 3D contextualization APIs for CAD, PointCloud and 360-images contextualization. These endpoints are in public preview. The Python SDK does not include these endpoints yet, so call them over HTTP. |
| Data catalog | 2026-10-15 | 2027-12-31 | We’re deprecating Data catalog. It remains available during the deprecation period. After the retirement date, it shuts down. Action required: Move to the replacement user interface when it launches in 2027, and complete the move before December 31, 2027. |
| Data explorer | 2026-10-15 | 2027-12-31 | We’re deprecating Data explorer. It remains available during the deprecation period. After the retirement date, it shuts down. Action required: Use Search in the Flows workspace to find and preview industrial data. |
| Asset-centric Cognite InField | 2026-10-15 | 2027-12-31 | We’re deprecating Cognite InField when it runs on asset-centric resources. InField on the core data model remains available. Action required: Configure InField on the core data model before December 31, 2027. You can upgrade InField with the migration plugin. |
| Asset-centric Cognite Maintain | 2026-10-15 | 2027-12-31 | We’re deprecating Cognite Maintain when it runs on asset-centric resources. Maintain on the core data model remains available. This row is separate from Maintain v1, which is already retired. Action required: Configure Maintain on the core data model before December 31, 2027. |
| Asset-centric OData service | 2026-10-15 | 2027-12-31 | We’re deprecating the asset-centric OData service for assets, events, sequences, and asset-centric file and time series metadata. The service remains available during the deprecation period. After the retirement date, those resources shut down. The data modeling OData service stays available. RAW stays available. This row is separate from the Power BI OData connector, which is already deprecated. Action required: Move queries to the data modeling OData service before December 31, 2027. |
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. |
| Runtime v3 for Cognite Functions on Azure | 2026-09-30 | 2026-09-30 | Microsoft Azure will stop running Azure Functions runtime v3 on Linux Consumption on September 30, 2026. Cognite Functions on Azure that still use runtime v3 stop running on that date. Cognite switched the default deployment configuration to runtime v4 on November 18, 2022 (November 22, 2022 for the az-power-no-northeurope cluster). Functions deployed after those dates already use runtime v4. No actions necessary. Action required: Between July and September 2026, audit your active functions deployed on or before those dates, verify code and dependency compatibility with runtime v4, and redeploy affected functions before September 30, 2026. Redeployments automatically use runtime v4. Check function call logs after redeployment. Redeploying also addresses the separate current backend for Cognite Functions on Azure deprecation listed below. If your functions use Python 3.10, update the Python runtime to 3.11 or later before October 1, 2026 — see Python 3.10 in Cognite Functions below. |
| 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. Redeploying for runtime v3 on Azure (see row above) also moves functions to the new backend. |
| 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.11 in Cognite Functions | 2026-10-20 | 2027-10-20 | Update the Python runtime to version 3.12 (py312) or later to continue using Cognite Functions. Redeploying for Azure runtime v4 does not change the Python version. |
| 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. If you audit functions for runtime v3 on Azure (see row above), update the Python runtime separately. Redeploying for runtime v4 does not change the Python version. |
| 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-12-31 | 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 December 31, 2026. |
| 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. |