> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Jobs JSON Object

## Article: Jobs JSON Object

## Article Link: https://dev.wix.com/docs/develop-websites/articles/workspace-tools/developer-tools/recurring-jobs/jobs-json-object.md

## Article Content:

# Jobs: JSON Object 

When scheduling [recurring jobs](https://dev.wix.com/docs/develop-websites/articles/workspace-tools/developer-tools/recurring-jobs/about-scheduling-recurring-jobs.md) on your site, you define the jobs in the `jobs.config` file. The `jobs` object in the file is structured as follows:

```json
{
  "jobs": [
    {
      "functionLocation": "<FILE PATH>",
      "functionName": "<FUNCTION NAME>",
      "description": "<JOB DESCRIPTION>",
      "executionConfig": {
        "<CONFIGURATION THAT DEFINES WHEN THE JOB RUNS>"
      }
    }
  ]
}
```

| Property           | Type | Required |
| ------------------ | ---- | -------- |
| [`functionLocation`](#functionlocation) | String | Yes |
| [`functionName`](#functionname)     | String | Yes |
| [`description`](#description)      | String | No  |
| [`executionConfig`](#executionconfig)  | Object | Yes |

Here is an example of a JSON object configured to send a status report every Monday morning at 8:00 AM UTC time:
```json
{
  "jobs": [
    {
      "functionLocation": "/utils.web.js",
      "functionName": "sendStatusReport",
      "description": "Send a weekly status report.",
      "executionConfig": {
        "time": "08:00",
        "dayOfWeek": "Monday"
      }
    }
  ]
}
```

## `functionLocation`
Path to the backend file that contains the function you want to run at the scheduled time. The function location is a relative path within the **Backend** folder. The function can be in any backend `.js`, `.web.js`, or `.jsw` file.

## `functionName`
Name of the function to run at the scheduled time.

> **Note:** Make sure that you export the function you want the job scheduler to run on.

## `description`
Optional description of the job.

## `executionConfig`
Object that contains information about when the job should run, using either a cron expression or time configuration properties.
> **Notes:**
> + All job configuration times are based on [UTC time](https://dev.wix.com/docs/develop-websites/articles/workspace-tools/developer-tools/recurring-jobs/about-scheduling-recurring-jobs.md#times).
> + Jobs occurring more than once a day must be defined with a cron expression.
> + If both methods below are added to a single `executionConfig` object, only the cron expression is used.

### `cronExpression`
Use a [cron expression](https://en.wikipedia.org/wiki/Cron#cRON_expression) as a single property in the `executionConfig` object.

For example, to run a job every day at 8:00 in the morning, use:
```json
{
  "executionConfig": {
        "cronExpression": "0 8 * * *"
  }
}
```

### `time`, `dayOfWeek`, `dateOfMonth`
Use multiple properties, `time`, `dayOfWeek`, `dateOfMonth`, to schedule the job. `time` is the only required property with this method. 
If a job includes both `dayOfWeek` and `dateOfMonth`, an error occurs and the job will not run.

+ `time` The time of day the job runs. The time is specified as [UTC time](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) in `HH:MM` format.
+ `dayOfWeek` One of: `Sunday`, `Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, or `Saturday`
+ `dateInMonth` Number between `1` and `31`.

For example, to run a job every Sunday at 8:00 in the morning, use:
```json
{
  "executionConfig": {
        "time": "08:00",
        "dayOfWeek": "Sunday"
  }
}
```