# Blocking until transforms finish
##  Blocking until transforms finish
### Description
This transform simply waits until all the transform copies that are specified in the dialog have finished.
You can use it to avoid the natural concurrency (parallelism) that exists between pipeline transform copies.
| Hop Engine | ✓ |
| ---------- | ------------ |
| Spark | ? |
| Flink | ? |
| Dataflow | ? |
### Options
| Option | Description |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| Transform name | Name of the transform. |
| Watch the following transforms | Use this grid to specify the transforms to wait for. |
| Get transforms | Push this button to auto-fill the "Watch the following transforms" grid with all transforms available in the pipeline. |
| Option | Description |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Transform name | The name of the transform to wait for. |
| CopyNr | The (0-based) copy number of the transform. If the named transform has an explicit setting for "Change number of copies to start", and you want to wait for all copies to finish, you’ll need to enter one row in the grid for each copy, and use this column to specify which copy of the transform to wait for. For the default number of copies (1), the CopyNr is always 0. |
---
# 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.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/blockuntiltransformsfinish.md?ask=
```
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.