ZenotiHelp

Region-level background job configuration

ZTZenoti Docs Team Updated August 16, 2026 4 min readGuide

Zenoti Payments runs background jobs that process recurring payment tasks — such as dunning retries and scheduled collections — on a defined schedule. This article explains how to enable or disable individual background payment jobs per region and how to adjust how frequently each job runs, without requiring a code deployment.

Note: For conceptual background on how Zenoti Payments processes recurring payments, see Payments Overview.

Before you begin

  • You must have access to region-level payment configuration settings in your organization.
  • Confirm which payment regions your organization operates in before making changes. Disabling a job for a region stops all processing that job performs in that region until it is re-enabled.

Important: Changes to job intervals take effect on the next scheduled execution cycle. Disabling a job stops it immediately for the affected region but does not affect other regions.

Steps

Review the current job configuration for a region

Before enabling, disabling, or adjusting a job, confirm the current state for the target region.

  1. Contact your Zenoti administrator or implementation team to access the region-level background job configuration settings.
  2. Identify the region you want to configure.
  3. For each background payment job listed for that region, note:
    • Enabled — Whether the job is currently active (true by default) or disabled.
    • Interval — How frequently the job runs, expressed in minutes or another time unit configured for that job.

Note: Each background payment job is configured independently per region. A job that is enabled in one region may be disabled in another without affecting either region's other jobs.

Enable or disable a background job for a region

Each background payment job can be independently enabled or disabled for a given region. By default, all jobs are enabled (true).

  1. Identify the specific background payment job you want to change.
  2. Identify the region for which you want to change the job's state.
  3. Set the enabled value for that job in that region:
    • Set to true to enable the job (default).
    • Set to false to disable the job.
  4. Confirm the change with your administrator. The job state takes effect at the next execution cycle.

Important: Disabling a background job stops all processing that job performs in the affected region. For example, disabling a dunning retry job for a region means failed recurring payment retries will not run in that region until the job is re-enabled. Verify the operational impact before disabling any job in a production region.

Adjust the execution interval for a background job

The execution interval controls how frequently a background payment job runs for a specific region. Adjusting the interval lets you tune job frequency independently across regions without a code deployment.

  1. Identify the background payment job whose interval you want to adjust.
  2. Identify the region for which you want to change the interval.
  3. Set the interval value for that job in that region to the desired frequency.
  4. Confirm the change with your administrator. The new interval takes effect at the next execution cycle.

Note: Intervals are configured per region per job. Changing the interval for a job in one region does not affect the interval for the same job in any other region.

Tips

  • Start with the default interval before tuning. The default interval for each job is set to balance processing throughput and system load. Only adjust intervals if you have a specific operational reason, such as a region with unusually high transaction volume or a region where processing latency is a known issue.
  • Disable jobs only when necessary. Disabling a background payment job in a region stops all processing that job performs there. If you need to pause processing temporarily — for example, during a maintenance window — plan to re-enable the job promptly to avoid a backlog of unprocessed recurring payments.
  • Coordinate interval changes across regions. If your organization processes payments in multiple regions, consider whether interval changes in one region will shift load to another. Staggering intervals across regions can help distribute processing more evenly.
  • Document your changes. Because region-level job configuration affects payment processing behavior, keep a record of any changes made, including the region, job name, previous value, new value, and the reason for the change.

Troubleshooting

Problem Likely cause Resolution
Recurring payments are not being retried in a region The dunning or retry job for that region may be disabled Check the enabled value for the relevant job in the affected region and set it to true if it is disabled
A job is running more or less frequently than expected The interval value for that job in that region may have been changed Review the current interval setting for the job and region, and restore it to the intended value
A change to the interval or enabled state does not appear to have taken effect The change takes effect at the next execution cycle, not immediately Wait for the next scheduled cycle to complete, then verify the job behavior
Was this article helpful?
Your feedback helps us improve our documentation.