Purpose
Explains a step result, successful completion or an error. A notification does not pause execution; a dialog waits for the user to close it. You can add a system card containing the run result.
Inputs and outputs
One in input and an optional out output; the table passes through unchanged. The message appears only on an active route.
Parameters
| Parameter | Settings and values | Options and limits |
|---|---|---|
title | The title shown to the user. | Default: ПовідомленняUp to 200 characters |
body | Message text, up to 4000 characters. | Default: emptyUp to 4000 characters |
display | toast — a brief notification; dialog — a dialog that waits. | Options: toast, dialogDefault: toast |
style | An informational, success or error notification appearance. | Options: info, success, errorDefault: info |
timeout | Automatically close a toast after 1–3600 seconds; 8 by default. | Default: 8Limits: 1…3600 |
wizard | Show the block as a step in the execution wizard. | Default: disabled |
system_info | Add system information about rows, duration, transfer direction or the error cause. | Default: disabled |
Step-by-step configuration
- Place the block on the required active branch; after a target, use success or failure.
- Enter the title and text.
- Choose a notification or dialog and, if needed, its style and timeout.
- Enable system_info to explain the result and wizard to display it among the steps.
Rules and diagnostics
- The error style does not itself make execution fail — it controls the message appearance.
- A dialog waits for the user. For a fully automatic message, use a delivery channel suitable for that type of run.
- The system card does not display data values, addresses or passwords.
- Returning to earlier wizard steps is possible until data has been written.
Configuration example
Connect the cube’s success output to a “Plan loaded” message with style=success, system_info=true. Connect failure to a separate “Write not completed” message with style=error, system_info=true.