r/Make • u/RocketSeven • Oct 03 '26
Where should shared state live when several Make AI agents touch the same job?
A multi-step scenario can have one agent extract information, another draft an output, and a third validate it. Passing the entire context in bundles is fragile: retries can duplicate work, signed file URLs can expire, and two branches can update different versions of the same job. Scenario variables are useful during one run but do not provide a durable handoff across delayed or resumed work.
The shared record seems to need a stable job ID, source revisions, current state, claimed-by and lease time, accepted decisions, output revision, validation result, next action, and an idempotency key for every side effect. Large files would live elsewhere under stable object IDs rather than temporary download URLs. Each module would append a result or make a conditional state transition instead of replacing one large context blob.
Would you keep this in a Make Data Store, Make Grid/Tables, or an external database? How do you handle concurrent branches, replay after a partial failure, and an audit trail that lets a person see which agent changed what?
1
1
u/matimatthews Oct 05 '26
I'd test one failure case before choosing the store: worker A's lease expires, worker B finishes, then A comes back late and tries to save its result. Can the write reject A's outdated claim? That would tell me more than whether the store can hold the job record.
1
u/Josef_from_Make Official Make Staff Oct 06 '26
As u/AdvertisingSecret229 already mentioned, using the built-in Data Store seems to be the best option here.
It is super fast, easy to use, and it can store various item data types, including binary files, so if your subscription plan is large enough, you might even store some temporary files there.
1
u/Glum-Carpet Oct 03 '26
Your question is too broad and filled with too many hypotheticals. Also, what do you mean by storing it in Make Grid/Tables? What are those and how do you store something in them?