Skip to content

mcp runtime expression: add precision on action condition. #471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
paulRbr merged 1 commit into from
Jul 7, 2026
Merged

mcp runtime expression: add precision on action condition. #471

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/_help/mcp-servers/runtime-expressions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,9 +271,9 @@ outputs:
> String interpolation only works with dot notation expressions. JMESPath expressions (containing `[*]`, `[0]`, functions, etc.) are resolved as a whole and cannot be combined with other expressions in the same string.
{: .warning}

## Conditions
## Action conditions

Expressions inside `when` clauses are resolved, then evaluated with standard operators.
Actions defined in a step can use expressions variables inside then `when` clause. Those are resolved, then evaluated with standard operators.

```yaml
actions:
Expand All @@ -288,6 +288,8 @@ actions:

Supported operators: `==`, `!=`, `>`, `<`, `>=`, `<=`, `AND`, `OR`, `!`.

> JMESPath functions are not supported inside action conditions. You should only use expression variables with a comparaison operator. You can however, use a function in a step `outputs` and then use the output in the condition, i.e. `$step.my-step.outputs.aggregated-result > 10`.
{: .warning}

## Complete example

Expand Down
Loading