Native LCA deprecation – Oct 2025 and Aug 2026
Learn about the phased deprecation of native LCAs and what it means for your tenants.
What are we deprecating?
We're deprecating the native Lifecycle Action (LCA) feature in two phases. Native LCAs are customer-authored code that currently run in Reltio’s environment. This deprecation applies to all tenants and includes changes to how new and existing native LCAs are supported.
This change affects the entire native LCA framework, including the ability to create, update, deploy, and run LCAs hosted in Reltio-managed infrastructure. Once deprecated, Reltio will no longer host or execute any customer-authored native LCAs, regardless of their deployment history.
Why are we deprecating it?
Native LCAs run in Reltio’s environment but are authored by customers. This can lead to performance or security issues, since the code isn't owned by Reltio. Poorly performing native LCAs can also impact other tenants hosted on the same node.
To reduce these risks, Reltio engineering manually reviews and approves all native LCAs before deployment. This manual review process creates delays for customers and increases engineering dependence.
When are we deprecating it?
-
October 24, 2025: New native LCAs can no longer be deployed or hosted.
-
August 31, 2026: Support for the native LCA feature ends entirely.
What does this mean to you?
-
If you have existing native LCAs, you can continue using and updating them until August 31, 2026.
-
After that date, native LCAs will no longer function or be supported.
What action do you need to take?
-
AWS Lambda
-
Google Cloud Functions
-
Azure Functions
Reltio will provide automated scripts, detailed documentation, and transition support. The goal is to make migration require minimal effort from your team.
Also, any new LCAs should be created only as cloud native functions.
Still have questions?
Customers using native LCAs will receive an email notification. For help or further details, contact the Reltio Customer Engineering team.