Memory¶
Memory lets a workflow remember things from one run to the next, such as the support tickets it has already handled. Later runs pick up where earlier ones left off.
When to use memory¶
Most workflows don't need memory. Each run collects what it needs and uses it within that run. Memory is for what has to carry over between runs:
- Not repeating work. A daily workflow that processes new orders remembers which ones it finished, so the next run skips them.
- Keeping track over time. A workflow remembers the date of its last sync or a running total, so the next run knows where things stand.
- Remembering judgment calls. A workflow can note how it handled an unusual case, so later runs handle it the same way.
Add memory to a workflow¶
Ask Malleable. For example: "Remember which invoices you've already sent, so the next run doesn't send them again." Malleable sets up the memory and the steps that use it. Like any change, it goes into a draft until you publish.
Memory stays with the workflow when you publish a new version. Test runs share it with live runs. If a test run marks an order as handled, live runs skip it too.
See what's in memory¶
- Click the workflow's name at the top of the canvas to open its settings.
- On the Settings tab, find Memory tables.
- Click a table to see what's in it.
Fix or clear memory¶
Sometimes memory needs a fix. For example, an order was marked as handled by mistake, or you want a fresh start after testing. Ask Malleable, for example: "Remove order 1042 from memory so the next run picks it up again," or "Clear the processed orders memory."
Malleable asks for your approval before it changes anything.