#Data Cloud62 人がディスカッション中

Hi @Mélina MOLHO

This is a known friction point with Data Cloud Data Graphs referencing CMS content a few likely causes, in order of probability:My best guess is step 2 (the 48-hour sync lag) or step 1 (Trash still holding them) those are the two most common causes for exactly this scenario. If you check the Recycle Bin and it's already empty, wait a day and retry before escalating. 

1. Check the CMS Recycle Bin 
   Deleting a form/landing page in Experience Builder or CMS Workspaces often just moves it to Trash, not a hard delete. Go to Digital Experiences > [your site or CMS Workspace] > Content > check for a Trash/Recycle Bin view, and permanently delete MCAIPBQMF5XVGJ7HLSXSOCBCQL54 and LP_NPS from there.

2. Wait out the known sync delay 
   Salesforce's own docs note that for Managed Content Resources specifically, a deletion can take up to 48 hours to be fully reflected in the dependency index, even though the item is gone from the UI. If you deleted these recently, this alone may explain it retry the delete tomorrow before troubleshooting further.

3. Confirm they're not still published/versioned elsewhere 
   A CMS form or landing page can have multiple published versions or be reused across more than one site/channel. Check Setup > Digital Experiences > All Sites, and also any other CMS Workspace, to confirm there isn't a second reference to the same content item still live.

4. Search for embedded references 
   sfdc_cms_form / sfdc_cms_landingPage content can be embedded as a component inside another Experience Builder page or an LWC. If either was ever dragged onto a page that still exists, that page is holding a live reference search Experience Builder pages for the component.

5. Use the Dependency API to get an authoritative list 
   If the UI dependency list looks stale, query MetadataComponentDependency (or the equivalent Data Cloud dependency Connect REST endpoint) to see exactly what's still pointing at the Data Graph, rather than trusting the UI panel alone.

6. Escalate to Salesforce Support if it persists 
   If it's still blocked after 48+ hours and steps 1–4 show nothing, this is worth a Support case Data Cloud's dependency checker referencing already deleted CMS resources is a reported pattern, not something you can force clear from the UI yourself.

My best guess is step 2 (the 48-hour sync lag) or step 1 (Trash still holding them) those are the two most common causes for exactly this scenario. If you check the Recycle Bin and it's already empty, wait a day and retry before escalating.  

I hope you find the above information helpful. If it does, Please mark it as Best Answer to help others too.

try to check the UDLO→UDMO transform job status in Data Cloud's job monitor. If it's not listed as running/completed, it was never triggered — this is the direct cause of "data reaches UDLO but UDMO stays empty.  Resource: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-awss3-udlo.html

The step your build may be missing or need to be enabled : UDLO → UDMO → 

Search Index (Easy Setup) → Data Explorer validation.  UDLO ingestion and UDMO population are two independently-triggered processes. File-notification wiring (Lambda → connected app → UDLO) only proves the first process. The second — chunking, embedding, and DMO population — is provisioned separately via the Search Index tab, and it's optional at UDLO creation time.  

 UDLO ingestion and UDMO/Search-Index population are separate, independently-triggered stages, and Job Monitor only reflects jobs actually provisioned. 

Let me know, if this is resolved.

Resolved by creating a new policy in Data Governance

Hi , 

Deactivating the Business Unit is not sufficient. The Data Space still appears to have a dependency on a Business Unit that contains one or more CMS Workspaces. Check the Marketing Cloud Business Unit for existing CMS Workspaces and remove any remaining Data Space mappings. Also verify whether any deployed Data Kits are still associated with the Data Space before attempting deletion again. 

Hi @Alyssa Jenson , I put Agentforce Coworker

to work on a single account and saved serious time. From one screen, I compared two promotions, checked the customer sentiment score and updated contact details instantly.  

It’s a game‑changer for efficiency and customer experience — all in just a few clicks! 

Link:

Hello, 

For a local handyman or home-service website, I’d keep the design simple, clean, and action-focused—visitors should immediately understand what services you offer, where you serve, and how to contact/book you. Use a clear homepage structure with a strong hero section, a short list of key services, reviews, before/after photos, service areas, pricing or “get a quote” CTA, and a simple contact section. Keep the colors consistent (2–3 main colors), use plenty of whitespace, and make buttons like Call Now / Get a Quote / Book a Service easy to spot, especially on mobile. Before calling the design finished, I’d test it on different phone sizes, check loading speed, make sure every link and form works, confirm the phone number is clickable, check spelling/content, add trust signals like reviews and licenses/insurance if applicable, and make sure a first-time visitor can figure out what you do, where you work, and how to hire you within a few seconds. Hope this helps!

Hi @Ionuț Buzatu

- It seems like a  Data Kit/deployment limitation or Salesforce issue 

• Check the deployment logs for the detailed error.
•  Verify SFMC connector authorization in the target org. 
•  If individual SFMC streams still fail, raise it with Salesforce Support as a Data Cloud Data Kit deployment issue.