---
title: "MGS3040: a job check its worker cannot run"
description: Fires when a job record's check names an unknown project or target, a command the guard denies, a check only a person may run, or a run that skips the tests of the packages the job writes. The record is refused; name a check the worker can run to a passing record.
tags: [MGS3040, jobs, leases, fork, apply, agents, validation, check]
---

# MGS3040: a job check its worker cannot run

`magus job fork`, `magus job apply` and `magus\job.put` refused a job record
whose check its worker could never run to a passing record:

```text
[MGS3040] check.target "tset" is not a target of project ".": name one
  `magus describe targets` lists
```

Nothing was written to the job store.

## What fires it

- A check naming a project or a target the workspace does not have.
- A check the guard would deny the worker, including one only the lease gate
  lets through.
- A check only a person may run.
- A check whose arguments narrow away the tests of the packages the job writes,
  such as a `-run` that matches none of them.

## Why

The check is the evidence the job is accepted on. A check the worker cannot run
leaves it with no way to finish, and the refusal comes after the work is done.

## What to do

Name a target the workspace has, in the project the job writes, with arguments
that still run the tests of the packages it changes. `magus describe targets`
lists the targets.

## See also

- [Leases](../../../guides/integrations/agents/leases.md): the check and how a worker is graded.