> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/workflows/or.md).
# Or
The *Or* task works in a similar manner to the logic operator “OR”. It returns a true value if any one of its arguments is true, otherwise, it returns false.
To use an OR logic operator task, drag-and-drop the *Or* task object onto the workflow designer.
The *Or* task object can be used with all workflow tasks. These tasks can include *Decision*, *Run Dataflow*, *Run Workflow*, etc.
The *Or* task object does not have a dedicated configuration window. However, a *General Options* window will open if you right-click on its header and select *Properties* from the context menu.
This window appears as the last screen of the configuration window for all flow objects.
The *Comments* input allows you to enter comments associated with this object. These comments appear as you hover over the object.
* *Clear Incoming Record Messages*: Removes any message attached with a record, these could be an error or a warning message.
* *Do Not Process Records with errors*: Filters out all the erroneous records from the incoming data set.
* *Do not Overwrite Default Values with Nulls*: Prevents Astera from overwriting any previously assigned default value with a null value.
The following is an example of using the *Or* object in a workflow:
Here, you can see that if the *CustomersData* ends in error or *OrdersData* ends successfully, then the *FileTransfer* task will get triggered. This means that if either of the tasks associated with *Or* meets the specified criteria, then the subsequent task/tasks will be triggered.
This concludes the configuration and working of the *Or* workflow task in Astera.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.astera.com/astera-data-stack-v10/workflows/or.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
