> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genesiscomputing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Genesis Job Tools

> Control and monitor Genesis background jobs. List, start, stop, and follow system jobs that power harvesting, maintenance, and health checks.

## **Overview**

### **Tool Name**

```json theme={null}
genesis_job_tools
```

### **Purpose**

The **genesis\_job\_tools** provide management for background jobs and periodic maintenance across the platform. Use them to list available jobs, start or stop specific processes, and follow live logs for troubleshooting and operational visibility.

### **Key Features & Functions**

<Steps>
  <Step title="List Jobs" icon="list">
    Discover available background jobs with names, status, and last run info.
  </Step>

  <Step title="Start Jobs" icon="play">
    Kick off harvests, maintenance, or monitoring tasks on demand.
  </Step>

  <Step title="Stop Jobs" icon="stop">
    Safely stop jobs during maintenance or incident response.
  </Step>

  <Step title="Follow Logs" icon="file-lines">
    Stream real-time output to diagnose issues as they occur.
  </Step>

  <Step title="Update Data Agent Activity" icon="robot">
    Refresh the data agent activity table so dashboards reflect current availability.
  </Step>

  <Step title="Scheduling Control" icon="clock">
    Manage execution parameters and cadence for optimal performance.
  </Step>
</Steps>

## **Input Parameters for Each Function**

### **`genesis_job`**

**Parameters**

| **Name** | **Definition** | **Format** |
| - | - | :-: |
| **action** | Operation to perform on the job subsystem. One of `list` `start` `stop` `follow`. | String |
| **job\_name** | Target job name for `start` `stop` or `follow`. Omit when using `list`. | String |

<Tip>
  Run `action: list` first to confirm the exact `job_name` and current status before starting or stopping anything.
</Tip>

### **`update_bots_active_table_tool`**

This function does not require parameters. It updates the data agents' active table with current availability and timestamps.

## **Use Cases**

1. **Maintenance windows**
   * Pause non critical jobs, perform upgrades, then resume services.
2. **Harvest oversight**
   * Start a metadata harvest and follow logs to verify schema coverage.
3. **Health monitoring**
   * Track long running monitors and confirm they are healthy after a deploy.
4. **Incident response**
   * Stop a noisy or failing job, inspect logs, then restart with adjusted settings.
5. **Operational hygiene**
   * Refresh the data agent activity table so status dashboards stay accurate.

<Warning>
  **Stopping core jobs can impact search, harvesting, or monitoring.** Confirm dependencies and maintenance windows before issuing `stop`.
</Warning>

## **Workflow/How It Works**

1. **Inventory**
   Use `action: list` to see jobs, status, and last run time.
2. **Control**
   Start or stop a specific job with `action: start` or `action: stop` and the exact `job_name`.
3. **Observe**
   Use `action: follow` to stream logs for a running job and watch progress in real time.
4. **Refresh**
   Call `update_bots_active_table_tool` to sync data agent availability after changes.

<Note>
  Following a very long-running job can produce large output. Limit follow sessions to investigation windows to conserve resources.
</Note>

## **Integration Relevance**

* **harvester\_tools** to manage catalog crawls that power metadata search.
* **system\_stats\_tools** to correlate job activity with performance metrics.
* **make\_baby\_bot** to reflect accurate data agent availability after lifecycle changes.
* **data\_connector\_tools** to validate connectivity when jobs interact with databases.
* **system\_manager\_tools** for broader admin workflows and audit trails.

## **Configuration Details**

* Job names must match the system registry exactly. Use `list` to copy the canonical name.
* Job control requires appropriate permissions. Coordinate with admins for production changes.
* Following logs streams live output and can increase load if many sessions are open.
* Some jobs have external dependencies like network or warehouse credits; verify before `start`.
* Data Agent activity updates should be scheduled regularly in environments where data agents scale up and down.

## **Limitations or Notes**

1. Job control often requires administrator privileges.
2. Not all jobs are stoppable if they provide critical platform functions.
3. Log streams can be verbose on large jobs and may time out for very long sessions.
4. High system load can delay job starts or extend runtimes.
5. Background jobs can have complex dependency chains; stopping one may affect others.

### **Output**

* **Job Listing**
  Array of jobs with name, status, description, and last execution details.
* **Job Control**
  Clear confirmation after `start` or `stop`, including new status and timestamps.
* **Log Follow**
  Real time output for active jobs to aid troubleshooting and verification.
* **Data Agent Activity Update** Confirmation that the data agent's active table was refreshed, with a completion timestamp.