# Job QScan Action

With the help of the Job QScan Action it is possible to transfer a file directly to QScan via a stream in order to carry out the necessary QC of this file with a template defined via the node. For this, the corresponding template must be created in QScan and the storage location of the file that is to be transferred must be made known to QScan beforehand (repository). QScan returns the analysis result in the form of markers and these can be further processed in the further course of the stream (transfer to Cosmo and Premiere).

#### Example:

As an example workflow, it would be possible to transfer every exported file to QScan in order to check the result technically. If an error is found (defined search for parameters via QSCAN template possible) this can be used as a condition to change the further course of the stream and to send the user a message. Another variant would be that an exported file would be transferred to QSCAN ({job.destination} from AME), then checked into COSMO (same project), and thereby automatically reimported into the open project. There the analysis results could be checked directly and any changes made.


---

# 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.helmut.de/helmut4-releases/v4.6.1/helmut4-components/streamdesigner/nodes/actions/job-action/job-qscan-action.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.