I love using Storage by Zapier as a simple place to build lists etc.
However, I’ve recently run into a problem where a Zap will be triggered twice at the same time, and so the storage value will be unpredictably modified. Example below where One zap was triggered twice instance1 and instance2 at the same time (or nearly the same time).
at 10:00:03 instance1 stored “xyz” into the storage key of “my-key”
at 10:00:04 instance2 stored “abc” into the storage key of “my-key”
(some other Zap Steps occurred)
at 10:00:10 instance1 pulled “my-key” from storage and got the value of “abc”
at 10:00:11 instance2 pulled “my-key” from storage and got the value of “abc”
I could fix this if I could grab a zap instance or task ID, so I could store “xyz” into “my-key-instance1” and the next instance would store “abc” into “my-key-instance2” and then the instances would pull their respective instance named keys.
I’ve tried things like grabbing a random value and storing that somewhere to use in the storage key name, but the moment I put it into a storage key the next instance will overwrite it (or might, depending on how fast the tasks are etc)
Essentially I want a way to have storage values be shared across all zaps/zap instances (this is the way it works now) But I also want a way to have this storage key/value be only available to this instance of this zap.
I’ve had to resort to adding a delay by queue which also adds an unnecessary 60 second delay/penalty on each instance of this zap.
Do you have any bright ideas on how to fix/overcome/solve this dilemma? From what I recall Zap Manager does not have a way to provide us with the current Zap instance/Task ID.
Best answer by PaulKortmanView original