This topic was automatically generated from Slack. You can find the original thread here.
hey! my workflows that created new keys in data stores started failing today or yesterday i think. i just emailed for support as well, could i get some help so my workflows stop failing? they’ve been running for the better part of a year now & i’d like to have them continue working
thanks!
We’ve actually been enforcing data store limits for some time, but fixed a bug today where that was not happening for some workspaces. So the fact that your workflows started failing today on writes is expected.
Have you seen the docs on limits and info on how to upgrade / reduce your usage?
yup, i went from a couple thousand keys to <500
but my number of stores is still too high
Yes, the number of data stores is a limit as well
any chance i can get an exemption on the number of stores? i don’t want to change my plan and leave the one i’m grandfathered into
Unfortunately we can’t give exemptions for this limit.
fair play
is there a new product i can use for kv stores? or are data stores still the recommended way to solve that?
Data stores are still the recommended built-in KV store, but you can always use a different store (like DynamoDB or Redis) if that helps
Or you could namespace your keys.
alright, i’m going to see if i can rewrite my workflows to share one store, or try something else
yeah, namespacing is my plan
but 500 keys is not a lot to work with
i’ll have to figure out how to evict keys, since i’m sort of using them as event IDs, so they only need to be there for a day or two
We do something like that on our side.