sn_ca.notification.max_users_per_event The sn_ca.notification.max_users_per_event property sets the maximum number of users that can be added to an email notification event. Administrators should review this setting to ensure it aligns with their notification strategy and system performance requirements.
1000The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property limits the number of users included in each email notification event to optimize processing and delivery. |
|---|---|
| What area does it affect? | Email Notification Management |
| What does the default mean? | The default value is "1000", which sets the baseline numeric behavior for this property. |
| When should you review it? | Review this property when adjusting email notification strategies or troubleshooting delivery issues. |
Raw metadata from the property record.
| Property name | sn_ca.notification.max_users_per_event |
|---|---|
| Sys ID | cf76f6b4eb001300a9e7e26ac106feb4 |
| Type | integer |
| Application | Content Experiences |
| Default value | 1000 |
| Description | The maximum number of users to add per event for Email |
| Updated | 2019-08-26 21:32:47 |
Official references and nearby text excerpts where this property appears.
sn_caOther properties in the same namespace.
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_run_time
This property limits the execution time of scheduled jobs for sending notifications, ensuring they finish proc
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
sn_ca.purging.max_run_time
This property defines the maximum run time for the Content Experiences scheduled job, limiting it to a specifi