Enrichment propagation behaves differently when you enable or disable autonomous enrichment at the global level. Enrichments created before enablement require a separate step to propagate.
Enrichment propagation behaves in the following ways:
•Eligible assets. Enrichments propagate only to assets that don't already have enrichments.
•Enabling. Tracking of enrichments begins from the date you enable autonomous enrichment at the global level on the Configure tab. Enrichments created after this date and time propagate to the catalog sources.
•Enrichments created before enablement. These enrichments don't propagate automatically. To propagate them, run the catalog source job and include the Autonomous Enrichment capability in the job. The job pulls all historical enrichments, with no time-range selection.
For information about how to run a catalog source job, see the catalog source documentation.
•Disabling. Future propagation stops. Enrichments that were already propagated or recommended remain unchanged, with no rollback.
•Source enrichment deletion. If a source enrichment is deleted, autonomous enrichment drops a recommended enrichment on the next run. An accepted enrichment is not deleted. If a source enrichment is updated, the update doesn't propagate.
•Source enrichment update. If a source enrichment is updated, autonomous enrichment updates the recommended enrichment on the next run. An accepted enrichment doesn't update.
•Rejected enrichments. You can reject an enrichment or a recommended enrichment. Future runs don't propagate these enrichments for that asset. You can undo the rejection later.