“LakeHouse TTL cannot be modified” for Adobe Analytics–sourced dataset

[aiya]

Hi,

I’m using Catalog Service API (PATCH v2) to update dataset attributes in CJA.

The same request works for other datasets, but for this specific dataset the API returns:

LakeHouse TTL cannot be modified for this dataset

After comparing the datasets, I noticed that the API works for datasets whose schema source is "Schema". The only dataset that fails has source "Adobe Analytics".

Is this behavior by design? Any official documentation about this?

Thanks!

[SamuelPaulPeter]

Yes — this is by design.

Datasets that originate from Adobe Analytics are system-managed datasets in AEP. Their Lakehouse TTL is controlled by Adobe, not by customers, so the Catalog Service API blocks any attempt to modify it.

That’s why:

• PATCH works for datasets created from custom schemas

• PATCH fails for datasets with source = Adobe Analytics

Adobe does this to protect downstream dependencies (Analytics processing, replays, backfills, and data consistency).

You cannot

• Modify TTL

• Change retention settings

• Override lifecycle controls
  for Adobe Analytics–sourced datasets

You can

• Control retention at the report suite / Analytics level

• Copy or export data into a custom dataset (schema-based) if you need custom TTL control

• Apply TTL changes only on non-Analytics datasets

[Sumit-Kumar]

Also, previously, AA data ingested into AEP Data Lake through source connector had no default retention and stayed indefinitely.
Last year, 2024, Adobe introduced AA Event Expiration (TTL) to align AEP's aa data retention with adobe analytics (default 25 months).

Enable TTL during for AA source connector setup Adobe Analytics source connector for report suite data | Adobe Experience Platform

Or you may check if changes to TTL for AA source connector can be done through customer care or your adobe acccount manager.