Loading
Prepare for Email to Become the Default Login ExperienceRead More
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
About Salesforce Data 360
Data 360 Marketing Agent Considerations and Troubleshooting

Data 360 Marketing Agent Considerations and Troubleshooting

Review the limits of the Data 360 Marketing Agent, and fix common problems such as missing criteria, a delayed response, or an attribute the agent can’t reach.

Required Editions

Available in: All Editions supported by Data 360. See Data 360 edition availability.

Considerations

  • Use the agent in one mode at a time. Don’t mix creating a segment from a Data 360 page with adding filters on the canvas by navigating between those pages in the same conversation.
  • Prefer the segment canvas when you want to add filters. The canvas gives you better feedback and lets you validate the segment as the agent works. Save the segment yourself; the agent doesn’t save.
  • The agent adds and builds filter criteria. It can’t remove or edit existing filters. Delete filters in the segment canvas.
  • The agent reads the last saved version of a segment. It can’t see unsaved changes on your canvas, so save before asking it to work with the current criteria.
  • The summary the agent gives after creating a segment can omit part of your request. Always check the criteria in the segment canvas.
  • If your request names a DMO or calculated insight that isn’t mapped, or that doesn’t appear in the attribute library on the left of the segment canvas, the agent can skip those objects without telling you. It then continues with the filters it can create. Check the canvas to confirm that every condition you asked for is present.
  • For highly complex requests, results can be inaccurate. Break the request into smaller parts and build the filters separately.

Troubleshoot the Data 360 Marketing Agent

Problem Troubleshooting Suggestions
A condition you asked for is missing from the segment.
  • Check the criteria in the segment canvas rather than the agent’s summary. Requests involving a spend or a total can be matched to an existing calculated insight that satisfies the amount but not the timeframe. Ask the agent to add the missing condition, or add it yourself in the canvas.
  • The same thing can happen when the request names a DMO or calculated insight that isn’t mapped or that doesn’t appear in the attribute library. The agent can ignore the missing object and proceed with the filters it can create, without telling you that something was skipped. Compare the canvas to your original request. If a condition is missing, name the object or attribute more specifically, or add the filter yourself.
Results are inaccurate.
  • Check that the Data 360 Data Q&A Agent is enabled. The Data 360 Marketing Agent relies on it to return accurate results. See Enable Data 360 Data Q&A Agent.
The agent says an attribute can’t be connected to your Segment On object.
  • No path exists between the two objects in your data model. Traversable paths come from the derived relationships that match and reconciliation rules generate. Choose an attribute the agent offers as an alternative. See Segment Canvas.
The agent offers an attribute that then fails.
  • The agent can offer an attribute that identifies a record or links two objects. Those attributes don’t appear in the segment canvas, so you can’t filter on them. Choose a different attribute. See Segment Canvas.
The Add filters button doesn’t appear.
  • The button appears in the Agentforce panel, directly beneath the agent’s response, not on the segment canvas. If the agent tells you the button is ready on the canvas, look in the panel.
  • The button also appears inconsistently, depending on whether the agent treated your request as editing the segment you have open or as creating a new one. If the button is missing, stay on the canvas, ask again, and name the segment you have open. Then save the segment yourself.
The agent asks the same question repeatedly.
  • When the agent restarts a request, it asks again about the segment type and publish schedule. Answer it again to continue.
The agent shows Something went wrong. Try again.
  • The agent backend can take longer than expected to respond. The Agentforce panel then shows
    Something went wrong
    . Reply with continue. The agent picks up where it left off and can finish the request.
  • This can happen after you answer a numbered list of attribute options. For example, you ask the agent to add a filter, it offers two attributes, you reply 1, and the panel shows the error. Type continue instead of starting over.
 
Loading
Salesforce Help | Article