Skip to content

Commit

Permalink
Update index.md
Browse files Browse the repository at this point in the history
  • Loading branch information
hhanova authored Oct 29, 2024
1 parent 04b8772 commit a49fe1f
Showing 1 changed file with 13 additions and 12 deletions.
25 changes: 13 additions & 12 deletions flows/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,7 @@ Let us show you how to organize individual tasks into steps, set up notification
- [Step 3: Execute tasks in parallel](#execute-tasks-in-parallel)
- [Step 4: Schedule and automate your flow](#schedule-and-automate)
- [Step 5: Set up notifications](#set-up-notifications)
- [Step 6: Continue on failure](#continue-on-failure)
- [Step 7: Check how your flow is running](#check-run-history)
- [Step 6: Check how your flow is running](#check-run-history)

## Access the Flow Builder
Select from the top menu **Flows -> Flows** and click the **Create Flow** button.
Expand All @@ -57,16 +56,23 @@ Use the plus icon to add other steps.

Typically, the flow starts with extractors, or, if all the tables you need are already in the project, it starts with transformations. To load your transformed data into your selected data destination, add one or more writers.

- Continue adding other ready-made components and organize them in a logical flow using the drag-and-drop functionality.
- Configure each component by providing the credentials and instructions for what or where to extract or write or for what code to execute in a transformation.
- Remember to adjust the input mapping of your transformation(s) to use the tables extracted from your selected data sources if necessary. Select the step and click **Edit Configuration**.
- You can also set **Task Parameters**, a low-level feature that modifies the parameters sent to the underlying [API call](https://developers.keboola.com/integrate/jobs/#run-a-job).
Continue adding other ready-made components and organize them in a **logical flow** using the drag-and-drop functionality.

Then configure each component by providing the **credentials** and **instructions** for what or where to extract or write or for what code to execute in a transformation.

Remember to adjust the **input mapping** of your transformation(s) to use the tables extracted from your selected data sources if necessary. Select the step and click **Edit Configuration**.

You can also set **Task Parameters**, a low-level feature that modifies the parameters sent to the underlying [API call](https://developers.keboola.com/integrate/jobs/#run-a-job).
To do this, select the task and click **Set advanced parameters**. When finished, click **Set**.

{: .image-popup}
![Task Parameters](/flows/task-parameters.png)

- Save the changes.
If you need to temporarily skip something, check the **Component enabled** flag. The task will then be excluded from the flow.

Finally, if you are working with APIs that are inconsistent or prone to frequent errors, consider enabling the **Continue on Failure** flag. Each phase (or step) of the flow will only run successfully if all jobs within that phase complete successfully. If a phase fails, no subsequent phases will continue. However, enabling this flag for each task (off by default) allows the flow to continue to subsequent phases, ending with a warning status if errors are encountered.

**Save** the changes.

Once you’ve built your flow end-to-end, it may look something like this:

Expand Down Expand Up @@ -120,11 +126,6 @@ You can set up an email notification to the following situations:
{: .image-popup}
![Set Up Notifications](/flows/notifications.png)

## Continue on Failure
Each phase (or step) of the flow runs successfully only if all jobs within that phase complete successfully.
If a phase fails, no subsequent phases will continue. To allow the following tasks to run despite errors, you can enable the **Continue on Failure** flag for each task (off by default).
This is particularly helpful when working with APIs that are inconsistent or prone to frequent errors.

Once everything is configured, the flow will automatically run at the scheduled time. Alternatively, you can run the entire flow manually by clicking **Run Flow**.

## Check Run History
Expand Down

0 comments on commit a49fe1f

Please sign in to comment.