> For the complete documentation index, see [llms.txt](https://flow-docs.cloudio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flow-docs.cloudio.io/getting-started-with-flow/flow-schedule.md).

# FLOW Schedule

There are three types of Input available in FLOW.

* **Pull**
  * e.g. Salesforce, Oracle, MySQL etc. which runs at a regular interval and polls for any changes in the source system.
* **Push**
  * Webhook to which the events get pushed by the source system
* **CDC**
  * e.g. Oracle CDC, MySQL CDC which listens for changes in real-time

All the pull inputs will be scheduled based on the Schedule Policy chosen at the time of flow creation.

![](/files/-Ly_Ze4wGoNS9qe7hBtB)

1. [**Cron Expression**](/getting-started-with-flow/flow-schedule/cron-schedule.md) - use this to schedule at a specific time of the day or day of the week/month etc using a cron expression
2. **Fixed Interval** - use this to schedule every x minutes
3. **After Parent Flow** - use this to define dependency between flows. You can choose to run this flow soon after the parent flow runs irrespective of the status.
4. **After Parent Flow Success** - similar to the above, but only runs if the parent flow completed without any errors.
5. **After Parent Flow Failure** - similar to the above, but only runs when the parent flow completed with errors.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flow-docs.cloudio.io/getting-started-with-flow/flow-schedule.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.