# Cosmo Get Project Sequences Action

The **Cosmo Get Project Sequences Action** node iterates through all sequences contained in a specified Cosmo project.

For each sequence found, the node triggers the following nodes in the stream and passes the corresponding sequence asset ID as the node result.

The result can be accessed using:\
[{job.assetId}](/helmut4-releases/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-assetid.md)

The node continues processing until every sequence in the project has been handled.

#### Input Parameters

**Project ID**\
ID of the project whose sequences should be processed.

#### Behavior

* Retrieves all sequences belonging to the project
* Executes the subsequent part of the stream once per sequence
* Provides the sequence asset ID as the job context
* Finishes successfully only after all sequences have been processed

If any downstream processing fails for a sequence, the entire node will be marked as failed.

<figure><img src="/files/Ld7aeSffLY7Bm7RvxLKr" alt="" width="348"><figcaption><p>Cosmo Get Project Sequences Action</p></figcaption></figure>

#### Practical Use

This node is designed for automated project-wide workflows. It allows operations to be performed on every sequence within a project without manually selecting them.

Typical use cases include:

* quality control checks
* batch exports
* report generation
* validation workflows
* automated publishing

#### Important Notes

* The node does not process media clips — only sequences (timelines/compositions)
* The node result represents the **sequence asset ID**, not a file path
* Subsequent nodes must be able to handle iterative execution

In simple terms:\
This node turns a project into a loop.\
Instead of handling one timeline, your stream automatically runs once for every sequence inside the project — which is what makes large project automation actually practical.


---

# 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/helmut4-components/streamdesigner/nodes/actions/cosmo-16/cosmo-get-project-sequences-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.