Executing the Segment Map

Synchronizing Subject IDs in the Data Mart and the Data Hub

If the Direct-only option is not enabled for your tenant, subject IDs must be uploaded to the data hub before you execute an on-premises segment map. The subject IDs must be uploaded to ensure that the SAS Customer Intelligence 360 identities are successfully mapped to the subject IDs for segments that are used when tasks are executed. If the Direct-only option is enabled, uploading subject IDs to the data hub is optional and on-premises segment maps can be used by direct marketing tasks only. For more information about SAS Customer Intelligence 360 identities, xFor more information, see Managing User Identities in SAS Customer Intelligence 360: Administration Guide.

Note: The option to not upload subject IDs to the data hub is available for tenants that are licensed for SAS 360 Direct only. If the tenant is licensed for any license other than SAS 360 Direct, the option should not be turned on. If the option is turned on, the on-premises segments would be unusable by the other task types that are associated with licenses other than SAS 360 Direct. For example, if a tenant is licensed for both SAS 360 Direct and SAS 360 Email, the subject IDs must be loaded into the data hub. For information about setting the option, contact your on-site SAS administrator.

If subject IDs have not been loaded to the cloud and the Direct-only option is not set, there is no pre-existing mapping between the data mart IDs and the SAS Customer Intelligence 360 identities.

IMPORTANT You do not need to load subject IDs to the cloud if you are using only direct marketing tasks. However, if you use or plan to use tasks other than direct marketing tasks (including Activities), you must load subject IDs to the cloud.

Execute the Segment Map

TipIf system issues cause the execution of a segment map to fail, the execution of any associated direct marketing tasks might be paused indefinitely. To ensure that the task execution is not paused when the execution of a dependent segment map fails, you can set a time-out value for the completion of the segment map execution. For more information, see Specify the Settings for a Business Context in SAS Customer Intelligence 360: Administration Guide.

On the Orchestration tab for a published segment map, select Run Now to immediately execute the flow, update counts on nodes, and update any segments that have been published.

Note: Be aware of these behaviors when executing the flow for a published segment map:

The modified date for the segment map is changed to the current date when you select Run Now.
The Run Now button is not visible when the segment map is locked by another user.

For information about node counts during the execution of a segment map, see About Node Counts during Execution.

Note: Depending on the queue setting for the agent, you might receive an error for an execution request that is received by the agent before the agent goes offline. If the Automatically clear queued requests when the agent comes back online setting is selected for the agent, the execution request is cleared when the agent is reactivated and an error message appears. In that case, you must re-execute the segment map. If the selection is not selected, then the execution request remains in the queue for the agent when the agent comes back online. For more information, see Direct Access Points in SAS Customer Intelligence 360: Administration Guide.

In some circumstances, such as when the direct marketing agent is down or there are errors in a custom stored process, a segment map might remain in the Running status for an indefinite amount of time. However, it is possible that the segment map appears to be unresponsive because the execution is taking a long time, even though the on-premises agent is running.

To address this issue, click the Activate the Non-Responsive Item button to move the status of the item from Running to Active, with an error. When the button is clicked, the following events occur:

Jobs that are associated with the segment map and that are currently running on the on-premises system run to completion.
Pending jobs for the segment map are prevented from running.
The segment map stops and returns to the Active status with an error message that is cleared when the item is republished or run again.
The segments in the map are set to the Failed status. If a task started the execution of the segment map, the task is also marked as failed. However, it is possible that the export is generated even though the occurrences are marked as failed.

Note:

When you click the Activate the Non-Responsive Item button, any existing counts in the segment map are cleared in response to the original execution request.
The Activate the Non-Responsive Item button is visible only to users with either the Super Admin role or the Configuration Admin role in SAS Customer Intelligence 360. For information about administrative roles, see Assign User Roles in SAS Customer Intelligence 360: Administration Guide.
The Activate Non-Responsive Item button is not visible when the segment map is locked by another user.

To prevent the item from being non-responsive in future executions, you might need to perform one of the following actions:

Ensure that the on-premises agent is active and functioning properly. A system administrator might need to verify the status of the agent.
Ensure that any custom stored processes that are used in the non-responsive item are working properly because errors in these processes can cause the item to become non-responsive.

Note: Clicking the Activate the Non-Responsive Item button changes the status of the execution occurrence to Failed. The occurrence (as displayed when selecting the Occurrence

History page) might remain in progress even after the item status changes from Running to Active.

Monitoring the Execution Progress

To monitor the progress of the execution of a segment map, navigate to OrchestrationExecution. On the Execution tab, you can view a progress bar that displays the percent completion status for the map execution. The tasks that are shown in progress are the task sequence steps that represent the steps in the segment map execution. Because the task sequence steps are derived from all the segment map nodes, the steps might not exactly correspond to each node. Instead, each task sequence step indicates the current execution step in the segment map. If an execution step fails, the progress bar is red and a warning sign is displayed. For information about the execution failure, click View information . You can also copy and paste the task ID from the ID column for that step to search the log for details about the failure.

Note: The value for the displayed Total completion time is the time interval between the overall request start time and the overall request end time as measured by the agent. The total completion time does not equal the total of the time values in the Duration column for all of the steps because some steps might be processed concurrently.

The displayed Total completion time represents only the time for the on-premises execution of the segment map and does not include any additional processing time by SAS Customer Intelligence 360.

To view a table that dynamically displays the progress of each execution step, click Show details. To hide the table, click Hide details. During the execution, the table dynamically displays the rows for each step and the Name, Type, Start Date, Duration, and Status columns for each step row. The step numbers determine the default order of the rows. You can manage the columns in the table. To display additional columns such as End Date, ID, Log Task #, Preceding Tasks, or Task ID, click Options then select Manage columns. To hide a column, click Options then select Hide column. As the execution progresses, the table rows are updated accordingly. The information in the created table can be used to compare the duration of the individual execution steps and the duration of the complete execution of the segment map.

To download a JSON file that includes the table that contains information about the execution steps, click Download Details.

About Node Counts during Execution

During the execution of a segment map, counts are conducted for only the following nodes:

nodes with the Mark node as segment option selected
nodes with the Always generate a count for this node option selected
nodes with the Mark node as linkable option selected within a segment map with the Use the most current data when referenced by a link option not selected
any Export node
any Process node

During the execution of the segment map, the agent counts and executes as few nodes as possible while conforming to the listed node count policy.

Last updated: August 18, 2026