# Job Management

> Your job management hub for creating, running, monitoring, and organizing all your data validation jobs.

Whether you're comparing datasets or checking data quality, everything starts here.

{% hint style="info" %}
A **Job** is a configured task that defines what data to validate, how to validate it, and which rules apply. Create, execute, monitor, and archive jobs all in one place.
{% endhint %}

![Job Management Dashboard](/files/ejgYXv20osBiKCWR5tun)

***

## 🚀 Getting Started: Create a New Job

Choose the type of validation job that fits your needs:

{% tabs %}
{% tab title="Compare Job" %}
**Validate differences between two datasets**

Perfect when you need to:

* 🔄 Compare production vs. staging data
* ✅ Verify data migrations
* 🔗 Check cross-system consistency
* 📊 Audit data synchronization

**Use Cases:**

* Source → Target migration validation
* Replication verification
* Backup integrity checks
* Multi-region consistency

[➕ Create a Compare Job →](/data-testing/jobs-and-workflows/index/compare-job.md)
{% endtab %}

{% tab title="Evaluate Job" %}
**Perform in-depth validations on a single data source**

Ideal for:

* 🏗️ Schema validation
* 📋 Constraint checking
* 📈 Data profiling
* ✅ Quality rule enforcement
* 🧪 Custom logic validation

**Use Cases:**

* Data quality checks
* Schema compliance
* Business rule validation
* Data governance audits

[➕ Create an Evaluate Job →](/data-testing/jobs-and-workflows/index/evaluate-job.md)
{% endtab %}
{% endtabs %}

***

## 💾 Your Saved Jobs

Find all your job configurations in one convenient location. The Saved Jobs dashboard makes it easy to manage and rerun your validation workflows.

### What You Can Do

**📂 Browse & Organize**

* View your complete job library
* Sort and filter by various criteria
* Group by purpose or data source
* Search for specific jobs

**▶️ Run Your Jobs**

Choose how you want to execute:

| Mode             | Purpose                                        | Best For        |
| ---------------- | ---------------------------------------------- | --------------- |
| **Standard Run** | Full validation with comprehensive checks      | Complete audits |
| **⚡ Quick Run**  | Fast execution for datasets under 500K records | Rapid testing   |

{% hint style="success" %}
**Quick Run** is optimized for speed when you're working with smaller datasets or doing iterative testing during job development.
{% endhint %}

**🛠️ Manage Your Jobs**

* **✏️ Edit** – Update configurations as your needs change
* **📋 Clone** – Copy an existing job as a template
* **🗑️ Delete** – Remove jobs you no longer need
* **📌 Archive** – Store completed jobs for reference

![Saved Jobs Dashboard](/files/FwJW8VegyjGR7amQcmve)

***

## ⚡ Quick Run: Fast Testing Mode

Need results faster? Quick Run is optimized for speed when working with smaller datasets or doing iterative testing.

### When to Use Quick Run

Use Quick Run for:

* 🧪 Testing new configurations
* 📊 Working with datasets up to 500K records
* 🔄 Need faster feedback during development
* ⏱️ Running frequent validation checks

**Execution Time Comparison:**

| Dataset Size        | Standard Run | Quick Run     |
| ------------------- | ------------ | ------------- |
| < 100K records      | 5-10 min     | 1-2 min       |
| 100K - 500K records | 10-30 min    | 2-5 min       |
| > 500K records      | 30+ min      | Not available |

### Quick Run Locations

You can access Quick Run from:

1. **Starting a new job** – Choose Quick Run mode
2. **Saved Jobs list** – Use the Quick Run button
3. **Job history** – Quick Run on previous configurations

![Quick Run Option](/files/NCxF02fmWt87vRo5ysGa)\
![Quick Run in Saved Jobs](/files/7cZfiXfgCr6BJMo4WuMU)

{% hint style="info" %}
**Pro Tip:** Use Quick Run to validate your job configuration with sample data before running a full-scale validation.
{% endhint %}

***

## 📊 Job History: Track Your Results

Review all your past job executions in one place. The Job History section gives you complete visibility into your validation activities.

### Key Features

**📋 Complete Audit Trail**

* Chronological record of every job execution
* Timestamps and status for each run
* User attribution and execution context
* Performance metrics and resource usage

**📈 Detailed Results**

Click on any Completed job to view full validation results and findings.

**Compare Reports:**

* [View Compare Job Report →](/data-testing/reports-and-results/index/compare-report.md)
* [View Evaluate Job Report →](/data-testing/reports-and-results/index/evaluate-report.md)

**🔍 Smart Filtering**

Quickly locate specific jobs using multiple filters:

-️ **Status**: Completed, Failed, Running, Pending

* 📅 **Date Range**: Filter by execution dates
* 🏷️ **Job Type**: Compare or Evaluate
* 🔤 **Job Name**: Search by name

![Job History View](/files/ZahESsYqHAYEPFuJrLzN)

***

## 📊 Job Status Reference

| Status        | Meaning                   | Action           |
| ------------- | ------------------------- | ---------------- |
| **Pending**   | Job queued for execution  | Wait or cancel   |
| **Running**   | Job currently executing   | Monitor progress |
| **Completed** | Job finished successfully | View report      |
| **Failed**    | Job execution failed      | Review errors    |
| **Paused**    | Job manually paused       | Resume or cancel |

***

## 🎯 Best Practices

{% hint style="warning" %}
**Job Management Best Practices:**

1. ✅ **Name jobs descriptively** - Include source, target, and date
2. ✅ **Schedule regular runs** - Automate validation workflows
3. ✅ **Monitor trends** - Track data quality over time
4. ✅ **Archive old jobs** - Keep dashboard organized
5. ✅ **Test with Quick Run** - Before running full validation
6. ✅ **Review failed jobs** - Address issues promptly
7. ✅ **Document rules** - Maintain job configuration documentation
   {% endhint %}

***

## 🔄 Job Workflow

```mermaid
graph TD
    A["Create Job"] --> B["Configure Data Sources"]
    B --> C["Define Validation Rules"]
    C --> D["Test Configuration"]
    D --> E["Run Job"]
    E --> F{"Completed?"}
    F -->|Success| G["Review Report"]
    F -->|Failed| H["Debug & Edit"]
    H --> E
    G --> I["Archive or Rerun"]
    style A fill:#e1f5ff
    style E fill:#fff3e0
    style G fill:#c8e6c9
```

***

## 📚 Related Documentation

* [Create Compare Job](/data-testing/jobs-and-workflows/index/compare-job.md)
* [Create Evaluate Job](/data-testing/jobs-and-workflows/index/evaluate-job.md)
* [Quick Run Guide](/data-testing/jobs-and-workflows/index/quick-run.md)
* [Comparing Jobs](/data-testing/jobs-and-workflows/index/compare-jobs.md)
* [Evaluating Jobs](/data-testing/jobs-and-workflows/index/evaluate-jobs.md)
* [Compare Report](/data-testing/reports-and-results/index/compare-report.md)
* [Evaluate Report](/data-testing/reports-and-results/index/evaluate-report.md)
* [Data Source Connectors](/data-testing/data-sources/index.md)

***

## ❓ FAQ

**Q: How many jobs can I create?** A: Unlimited jobs. Organize them using naming conventions and tags.

**Q: Can I schedule jobs?** A: Yes, schedule jobs to run automatically on specific dates and times.

**Q: What's the difference between Compare and Evaluate?** A: Compare validates two sources, Evaluate validates one source against rules.

**Q: Can I edit a running job?** A: No, but you can edit saved configurations before starting a new run.


---

# Agent Instructions: 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:

```
GET https://docs.qyrus.com/data-testing/jobs-and-workflows/index.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.