Commit e00dfabe authored by MikeyMJCO's avatar MikeyMJCO
Browse files

Merge branch 'martin.w-master-patch-28293' into 'master'

Update scheduled-jobs.md with info about multisite configuration (per https://civicrm.stackexchange.com/a/20989)

See merge request documentation/docs/user-en!471
parents 8d6fc33c 200e578b
......@@ -160,6 +160,9 @@ Inserts activity for a contact or a case by retrieving inbound emails from a mai
* Recommended frequency: hourly
* Parameters: *(none)*
!!! note "Multisite installs"
For [CiviMail in a multisite](#multisite), you must configure this job to run for each site (CiviCRM domain ID).
### Job.fetch_bounces {:#job_fetch_bounces}
Fetches bounces from mailings and writes them to mailing statistics
......@@ -248,6 +251,9 @@ Generates and sends a copy of the specified report instance to the email address
* Recommended frequency: every time cron job is run
* Parameters: *(none)*
!!! note "Multisite installs"
For [CiviMail in a multisite](#multisite), you must configure this job to run for each site (CiviCRM domain ID).
### Job.process_membership {:#job_process_membership}
Updates membership statuses
......@@ -344,3 +350,17 @@ Updates the reset_date on an email address to indicate that there was a valid de
* Parameters:
* `minDays` (optional)
* `maxDays` (optional)
## Considerations for Multisite / Multi domain {:#multisite}
For a [multisite/multi-domain installation](https://docs.civicrm.org/sysadmin/en/latest/setup/multisite/), most jobs only need to be configured to run on one site, which is usually the primary domain site, which is to say, the site with CiviCRM domain ID 1.
Most jobs are not "domain-aware" and do not utilize the CiviCRM domain ID, so running such jobs only on the primary domain site is sufficient. Since the primary domain site includes all the standard jobs by default, it's a sensible place to put any additional jobs which are not domain specific. (Whether or not a job is domain-aware depends on the job itself but be aware the documentation may not explicitly state whether the job is domain-aware.)
For [**CiviMail in a multisite**](https://docs.civicrm.org/sysadmin/en/latest/setup/civimail/#civimail-in-a-multisite), there are two important jobs that are domain-specific and **must be run for each domain**:
* [`Job.process_mailing`](#job_process_mailing) ("Send Scheduled Mailings")
* [`Job.fetch_activities`](#job_fetch_activities) ("Process Inbound Emails")
When creating the above jobs for each site (or any other job with a duplicate API call), you must give the job a unique name, for example by appending the name of the site to the standard job name ("Send Scheduled Mailings - Site A"). Otherwise CiviCRM will complain about the duplicate name.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment