Property reference

sn_ca.purging.max_users_per_job

The sn_ca.purging.max_users_per_job property sets the maximum number of users that can be purged in a single job run. Admins should consider adjusting this value based on performance testing, especially in environments with large databases.

Default
25000
Type
integer
Application
Content Experiences

Key questions about this property

The 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 purged during each execution of the purge job, with a default setting of 25,000 users.
What area does it affect? Content Experiences
What does the default mean? The default value is "25000", which sets the baseline numeric behavior for this property.
When should you review it? Review this property when managing large user databases or optimizing purge job performance.

Out of the box property record

Raw metadata from the property record.

Property name sn_ca.purging.max_users_per_job
Sys ID 8adf18aa23001300fb0c949e27bf6579
Type integer
Application Content Experiences
Default value 25000
Description Max number of users to purge per job run
Updated 2018-03-16 15:37:19

Sources

Official references and nearby text excerpts where this property appears.

Documentation excerpt View supporting context
Context preview Snippet 1
... (sn_ca.purging.max_run_time) The maximum amount of time (in seconds) the Content Experiences: Purge Campaign Data scheduled job runs. Default value: 300 seconds Max number of users to purge per job run (sn_ca.purging.max_users_per_job) The maximum number of users to purge per job run. Default value: 25,000 Purge campaign data after the campaign ends (sn_ca.purging.purge_after_campaign_end) Purge all campaigns when the end date is reached. ...

More in sn_ca

Other properties in the same namespace.

All 32 properties in sn_ca →