Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.8.0
  • 5.7.6
  • 5.7.5
  • 5.7.4
  • 5.7.3
  • 5.7.2
  • 5.7.1
  • 5.7.0
  • 5.6.10
  • 5.6.9
  • 5.6.8
  • 5.6.7
  • 5.6.6
  • 5.6.5
  • 5.6.4
  • 5.6.3
  • 5.6.2
  • 5.6.1
  • 5.6.0
  • 5.5.6
  • 5.5.5
  • 5.5.4
  • 5.5.3
  • 5.5.2
  • 5.5.1
  • 5.5.0
  • 5.4.4
  • 5.4.3
  • 5.4.2
  • 5.4.1
  • 5.4.0
  • 5.3.42
  • 5.3.41
  • 5.3.40
  • 5.3.39
  • 5.3.38
  • 5.3.37
  • 5.3.36
  • 5.3.35
  • 5.3.34
  • 5.3.33
  • 5.3.32
  • 5.3.31
  • 5.3.30
  • 5.3.29
  • 5.3.28
  • 5.3.27
  • 5.3.26
  • 5.3.25
  • 5.3.24
  • 5.3.23
  • 5.3.22
  • 5.3.21
  • 5.3.20
  • 5.3.19
  • 5.3.18
  • 5.3.17
  • 5.3.16
  • 5.3.15
  • 5.3.14
  • 5.3.13
  • 5.3.12
  • 5.3.9
  • 5.3.6
  • 5.3.5
  • 5.3.3
  • 5.3.2
  • 5.3.1
  • 5.3.0
  • 5.2.14
  • 5.2.13
  • 5.2.12
  • 5.2.11
  • 5.2.10
  • 5.2.9
  • 5.2.5
  • 5.2.3
  • 5.2.2
  • 5.2.1
  • 5.1.1
  1. Docs
  2. /Release Notes
  3. /Release 5.7.6

Release 5.7.6

What Changed

  • Settings — Automatic Check: when creating or editing a schedule, you can set additional parameters for the selected Action Jail function — the same values you use in a scenario or when testing the action.
  • Scenario Builder: the toolbar always shows the active section name under the bot or process title — you no longer need to hover over the workflow name to see which section you are editing.
  • Scenario Builder — debugger: fixed hangs when testing a slider section that immediately transitions to another section via a cross-section link.

How It Changed

Before: An Automatic Check schedule ran the action without a way to pass parameters from the UI — only whatever was baked into the action. In Scenario Builder, the current section name lived in a tooltip on the workflow title. In the debugger, testing a slider section with an immediate jump to another section could loop indefinitely and never show the next step.

Now: Schedule parameters are configured in the create or edit form (when the action exposes a parameter schema — via a guided form or a text editor). The active section appears under the process name on wider screens and updates when you switch sections, change the URL, or run a test. The debugger correctly moves to the target section instead of restarting from the slider.

Why It Matters

Integrators can automate checks and background jobs more flexibly without duplicating actions for different parameter sets. Multi-section scenarios are easier to navigate in the editor. Testing complex cross-section flows is predictable and no longer blocks work in the constructor.

Related documentation

  • Create your first Automatic Check schedule
  • Processes and Scenarios — Scenario Builder
  • Scenario Builder hub
  • Slider node parameters
  • Cross-section flow
Prev
5.8.0
Next
5.7.5

On this page