sn_ca.add_users.max_run_time The sn_ca.add_users.max_run_time property sets the maximum duration in seconds for the scheduled job that updates campaign audiences. Admins should review this setting to ensure jobs complete efficiently without exceeding the defined time limit, which defaults to 1800 seconds.
1800The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property limits the execution time of the scheduled job responsible for updating campaign audiences, ensuring it finishes processing the current item within the specified duration. |
|---|---|
| What area does it affect? | Content Experiences |
| What does the default mean? | The default value is "1800", which sets the baseline numeric behavior for this property. |
| When should you review it? | Review this property when optimizing job performance or adjusting scheduled job durations. |
Raw metadata from the property record.
| Property name | sn_ca.add_users.max_run_time |
|---|---|
| Sys ID | b1dc7d9beb501300a9e7e26ac106fe9e |
| Type | integer |
| Application | Content Experiences |
| Default value | 1800 |
| Description | Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) |
| Updated | 2021-12-14 15:07:55 |
Official references and nearby text excerpts where this property appears.
sn_caOther properties in the same namespace.
sn_ca.add_users.event_stagger.campaign
It specifies the delay in seconds between campaign events during scheduled job execution, allowing for better
sn_ca.add_users.event_stagger.users
This property configures the delay between user addition events during the execution of the Content Experience
sn_ca.add_users.max_events
This property limits the number of events that can add users to a campaign, ensuring controlled processing dur
sn_ca.add_users.max_users_per_event
This property limits the number of users added per event to a maximum of 1,000, affecting how user additions a
sn_ca.all_must_approve
This property enforces that every approver must give their approval for scheduled content, impacting the publi
sn_ca.campaign.max_records_create
This property limits the number of records created per job run to optimize performance and resource usage duri
sn_ca.campaign.max_records_process
This property limits the number of targets processed per job run for campaigns, helping to manage system load
sn_ca.campaign.max_run_time
It limits the execution time of scheduled jobs related to Content Experiences, ensuring they finish processing