Variables

Read from Memory Block

Read from Memory reads a memory key and writes the value into a normal Flow variable.

At a glance

Best for

Persistent values

Requires

Memory key and output variable

Fallbacks

Null, empty, custom, or fail

Error handle

Yes

What it does

Read from Memory lets a Flow use state saved by earlier runs.

Use fallback behavior to decide what should happen when no memory value exists yet.

Use it when

Load the last seen ID before scraping a feed.
Read a checkpoint for a scheduled run.
Compare current page data with remembered state.

Do not use it when

The value only exists within the current run.
You need to save a new value; use Save to Memory or Track Change.
Missing memory should stop the Flow and no fallback is configured.

Settings

Read from Memory needs a memory key, group/scope, output variable, and missing-value fallback behavior.

Memory key

Required: Yes

Variables: Yes
Description: Key to read from persistent memory.

Memory group

Required: No

Variables: Yes
Description: Optional namespace for related memory keys.

Fallback mode

Required: No

Variables: No
Description: Choose null, empty, custom value, or fail when the key is missing.

Output variable

Required: Yes

Variables: Variable name
Description: Variable that receives the remembered value.

Setting	Required	Variables	Description
Memory key	Yes	Yes	Key to read from persistent memory.
Memory group	No	Yes	Optional namespace for related memory keys.
Fallback mode	No	No	Choose null, empty, custom value, or fail when the key is missing.
Output variable	Yes	Variable name	Variable that receives the remembered value.

Outputs

Read from Memory writes the remembered value to a normal variable.

{{outputVariableName}}any

Remembered value, fallback value, or null depending on settings.

foundboolean

Whether the memory key existed.

Example Flow

Read memory early when later Blocks need a persisted value to decide what to do.

Read the remembered value.
Compare or use it in later Blocks.
Save updated memory after the relevant work succeeds.

Errors and fixes

Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.

The output variable is empty.

Check: Check whether the key exists and which fallback mode is selected.
Fix: Use the correct key/group/scope or configure a custom fallback.

The Flow fails on the first run.

Check: Check whether fallback mode is set to fail.
Fix: Use null, empty, or custom fallback for first-run behavior.

Symptom	Check	Fix
The output variable is empty.	Check whether the key exists and which fallback mode is selected.	Use the correct key/group/scope or configure a custom fallback.
The Flow fails on the first run.	Check whether fallback mode is set to fail.	Use null, empty, or custom fallback for first-run behavior.

Local and cloud runs

Read from Memory is shared by local and cloud paths, but schedule-scoped memory should be verified for scheduled Cloud Runs.

Blocks

Understand how Blocks connect and pass state through a Flow.

Runs and outputs

Inspect Block output, errors, and variables after a run.