> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-3.-run-user-acceptance-tests-uat-in-a-multi-tenant-deployment-using-the-migration-wizard/jobs-multi-tenant.md).

# Jobs - Multi-Tenant

This section is relevant for child and development tenants. It is not relevant for the main tenant.

Jobs work the same way in Cortex XSOAR 6 and 8.

During the UAT phase, to avoid conflicts between the Cortex XSOAR 6 instance and the Cortex XSOAR 8 instance, jobs are disabled in Cortex XSOAR 8.

As the Cortex XSOAR 6 instance is still running jobs, performing the same jobs in the Cortex XSOAR 8 instance can lead to data issues, including duplicate data, duplicate emails, mirroring problems, and incidents reopening after being closed.

For testing purposes, you can override the default settings and enable jobs. After a job has been completed successfully and your testing is complete, we recommend disabling the job.

{% hint style="info" %}

### Tip

We recommend limiting the use of jobs on the Cortex XSOAR 8 instance until the migration is complete.
{% endhint %}

After the switchover date, jobs that were enabled in Cortex XSOAR 6 are enabled on the Cortex XSOAR 8 tenant. New jobs created in Cortex XSOAR 8 that did not exist in Cortex XSOAR 6 remain unchanged. Edited jobs created in Cortex XSOAR 8 will be overridden.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-multi-tenant-migration/migrate-from-cortex-xsoar-6-multi-tenant-to-cortex-xsoar-8-saas-multi-tenant-using-the-migration-wiz/step-3.-run-user-acceptance-tests-uat-in-a-multi-tenant-deployment-using-the-migration-wizard/jobs-multi-tenant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.