Cumulus Financial is experiencing delays in publishing multiple segments simultaneously and wants to avoid reducing the frequency of segment publishing while retaining the same segments. The best solution is to increase the Data Cloud segmentation concurrency limit . Here's why:
Understanding the Issue
The company is publishing multiple segments simultaneously, leading to delays.
Reducing the frequency or number of segments is not an option, as these are business-critical requirements.
Why Increase the Segmentation Concurrency Limit?
Segmentation Concurrency Limit :
Salesforce Data Cloud has a default limit on the number of segments that can be processed concurrently.
If multiple segments are being published at the same time, exceeding this limit can cause delays.
Solution Approach :
Increasing the segmentation concurrency limit allows more segments to be processed simultaneously without delays.
This ensures that all segments are published on time without reducing the frequency or removing existing segments.
Steps to Resolve the Issue
Step 1: Check Current Concurrency Limit
Navigate to Setup > Data Cloud Settings and review the current segmentation concurrency limit.
Step 2: Request an Increase
Contact Salesforce Support or your Salesforce Account Executive to request an increase in the segmentation concurrency limit.
Step 3: Monitor Performance
After increasing the limit, monitor segment publishing to ensure delays are resolved.
Why Not Other Options?
A). Enable rapid segment publishing to all to segment to reduce generation time :Rapid segment publishing is designed for faster generation but does not address concurrency issues when multiple segments are being published simultaneously.
B). Reduce the number of segments being published :This contradicts the requirement to retain the same segments and avoid reducing frequency.
D). Adjust the publish schedule start time of each segment to prevent overlapping processes :While staggering schedules may help, it does not fully resolve the issue of delays caused by concurrency limits.
Conclusion
By increasing the Data Cloud segmentation concurrency limit , Cumulus Financial can alleviate delays in publishing multiple segments simultaneously while meeting business requirements.

To create segments of users based on their Customer Lifetime Value, the customer needs to first ingest the source data into Data Cloud, then map the data to the Customer 360 data model, then create a calculated insight using the formula editor, and finally use the calculated insight in segmentation. Reference: [Data Ingestion], [Data Mapping], [Calculated Insights], [Segmentation]

These three components of Data Cloud can be bundled within a Data Kit. A Data Kit is a package that contains data model objects, segments, and data streams that can be installed in another Data Cloud org.References: https://help.salesforce.com/s/articleView?id=sf.c360_a_data_cloud_data_kit.htm&type=5

When disconnecting a data source in Salesforce Data Cloud, the system checks for active dependencies that rely on the data source. Based on Salesforce's official documentation (Disconnect a Data Source), the error occurs if the data source has data streams or segments associated with it. Here's the breakdown:
Key Dependencies That Block Disconnection
Data Stream (Option B):
Why It Matters:A data stream is the pipeline that ingests data from the source into Data Cloud. If an active data stream is connected to the data source, disconnecting the source will fail because the stream depends on it for ongoing data ingestion.
Resolution:Delete or pause the data stream first.
Documentation Reference:"Before disconnecting a data source, delete all data streams that are associated with it." (Salesforce Help Article) Segment (Option C):
Why It Matters:Segments built using data from the source will reference that data source. Disconnecting the source would orphan these segments, so the system blocks the action.
Resolution:Delete or modify segments that depend on the data source.
Documentation Reference:"If there are segments that use data from the data source, you must delete those segments before disconnecting the data source." (Salesforce Help Article) Why Other Options Are Incorrect Activation (A):Activations send segments to external systems (e.g., Marketing Cloud) but do not directly depend on the data source itself. The dependency chain is Segment # Activation, not Data Source # Activation.
Activation Target (D):Activation targets (e.g., Marketing Cloud) are destinations and do not tie directly to the data source.
Steps to Disconnect a Data Source
Delete Dependent Segments:Navigate to Data Cloud > Segments and remove any segments built using the data source.
Delete or Pause Data Streams:Go to Data Cloud > Data Streams and delete streams linked to the data source.
Disconnect the Data Source:Once dependencies are resolved, disconnect the source via Data Cloud > Data Sources.

The data types can be changed during ingestion before the Data Source Object (DSO) is created. A DSO is a container for ingested data that defines the schema, format, and metadata of the data. Data types can be changed in the Data Explorer before creating a DSO by using the Edit Schema option. Once a DSO is created, the data types cannot be changed. References: Create a Data Source Object