# \_statusSet

Sets the status of Jobs from Complete to Processed

### Parameters

#### ids

The IDs of the Jobs.

#### status

The status of the Jobs, this is required to be 2 for complete.

#### status\_ind

Optional parameter with more detail on the Job status, can be:\
"completed-processed" or "incomplete-completed"

### Example

```
FM_api('Jobs_statusSet', [
    'ids'=>[
        '1',
        '2',
        '3'
    ],
    'status' => '2'
]);
```

### Results

#### On Failure

If the "status" parameter is not set:

```
{"error":"missing or invalid parameter: status"}
```

If the "ids" parameter is not set:

```
{"error":"missing or invalid parameter: ids"}
```

If any of the IDs do not match existing Jobs:

```
{"errors":["Job does not exist: 2","Job does not exist: 3"]}
```

If "status\_ind" is set to 'completed\_processed' and "status" higher than 1, but a Job does not have it's meeting completed:

```
{"errors":["Job 2 is not yet complete."]}
```

If "status\_ind" is set to 'incomplete-completed' and there are Jobs which already have completed meetings.

```
{"errors":["Job 2 is already complete."]}
```

#### On Success

```
{"errors":[]}
```


---

# 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.fieldmotion.com/fieldmotion-api-docs/jobs/_statusset.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.