sn_ca.notification.max_run_time The sn_ca.notification.max_run_time property sets the maximum run time in seconds for scheduled jobs related to notifications. Admins should be aware of this setting to ensure that jobs complete processing within the defined time frame, 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 scheduled jobs for sending notifications, ensuring they finish processing the current item without starting new tasks. |
|---|---|
| What area does it affect? | Content Experiences Notifications |
| 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 adjusting notification job performance or troubleshooting delays. |
Raw metadata from the property record.
| Property name | sn_ca.notification.max_run_time |
|---|---|
| Sys ID | 2c0c02a8ebcc1300a9e7e26ac106fe83 |
| 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:20:46 |
Official references and nearby text excerpts where this property appears.
sn_caOther properties in the same namespace.
sn_ca.glide.script.block.client.globals
This boolean property, when set to true, prevents the use of global variables in client-side Glide scripts, en
sn_ca.min_admin_count
It enforces a minimum of two active admin users for Content Experiences, preventing system misconfiguration an
sn_ca.notification.event_stagger
It configures the interval for staggering notification events to optimize processing during scheduled jobs.
sn_ca.notification.max_events
This property limits the number of email events queued for processing during scheduled jobs, impacting the eff
sn_ca.notification.max_users_per_event
This property limits the number of users included in each email notification event to optimize processing and
sn_ca.publish.campaign.immediately
This property enables immediate triggering of the campaign publishing process, bypassing scheduled jobs and al
sn_ca.purging.days_after_campaign_end
It determines the delay period for purging campaign data following the end of a campaign, allowing for data re
sn_ca.purging.days_after_user_removed
It specifies the duration in days for delaying the purging of campaign data after a user has been removed from