sn_ca.user_deactivation.max_run_time The sn_ca.user_deactivation.max_run_time property sets the maximum run time in seconds for the scheduled job that deactivates flagged users. Admins should monitor this setting to ensure jobs complete efficiently, especially in environments with a large number of users.
300The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property defines the maximum duration for the Content Experiences scheduled job that deactivates users, defaulting to 300 seconds. |
|---|---|
| What area does it affect? | User Deactivation Processes |
| What does the default mean? | The default value is "300", which sets the baseline numeric behavior for this property. |
| When should you review it? | Review this property when adjusting job performance or managing a large user base. |
Raw metadata from the property record.
| Property name | sn_ca.user_deactivation.max_run_time |
|---|---|
| Sys ID | cd12092e23401300fb0c949e27bf652d |
| Type | integer |
| Application | Content Experiences |
| Default value | 300 |
| Description | Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) |
| Updated | 2018-03-16 15:31:52 |
Official references and nearby text excerpts where this property appears.
sn_caOther properties in the same namespace.
sn_ca.state_management.max_records_update
This property limits the number of records updated per job run to enhance processing efficiency and prevent sy
sn_ca.state_management.max_run_time
This property defines the maximum run time for scheduled jobs related to content state management, influencing
sn_ca.task.max_records_create
This property limits the number of records created by the Content Experiences scheduled job, impacting how eff
sn_ca.task.max_run_time
This property limits the execution time of scheduled jobs, allowing them to finish current tasks without picki
sn_ca.user_deactivation.max_users_per_job
This property limits the number of users deactivated per job run to optimize performance during scheduled deac
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