Skip to main content

v1.17 — October 2026

This release adds three cache nodes and lets you create a workflow without a trigger. A manual trigger run asks for the tracing mode, as a replay already does. Workflow lists show the business edit date, and a trace detail shows who started a manual run.

Documentation: Cache nodes · Create a workflow · Call a workflow node · Traces · Replay a trace

New features​

Cache nodes​

The Cache group in the editor contains three nodes.

  • Write to cache stores a key and a value, with an optional time to live in seconds (TTL).
  • Read from cache reads the value stored for a key.
  • Delete from cache removes a key.

Apizr provides 50 MB of cache storage. You can also use your own Redis instance. Quotas, TTL, cipher and the output key are described in Cache nodes.

Workflow without a trigger​

When creating a workflow, Without a trigger saves a reusable workflow, called from another workflow by the Call a workflow node. See Create a workflow.

Manual run: tracing mode​

The form that starts a trigger includes the tracing mode, as on replay. It is prefilled with the workflow mode, or Standard when none is set. Complete shows the same performance warning as on replay.

Improvements​

Call a workflow node​

Stop workflow on failure is available on the node. On, the parent workflow stops if the sub-workflow fails. Off, the parent continues. See Call a workflow.

ForEach and Switch​

In simple mode, the collection field of ForEach and the variable fields of Switch accept a reference with or without double braces (context.toto or {{context.toto}}). Handlebars highlighting is shown in both cases.

HTTP Request node​

A multipart/form-data body can reference a file already present in the context with the file:: prefix, for example file::document. See HTTP Request.

General stability​

Various improvements to the general stability of the platform.

Documentation: Cache nodes · Create a workflow · Call a workflow node · Traces