Yeah exactly. If it’s 500 keys, you would have to make sure you don’t hit it
Feature request here is that there should be a meta api for pipedream objects. I’d love a way to check the trigger for history of invocations
from that I could just calculate what I want
counting things seems so basic, maybe that should be a function of datastores or another action
If I set workers to 1 will triggers just get queued and eventually processed?
This feature request is kinda similar
that’s probably the simplest solution, even though I don’t like it 
If I set workers to 1 will triggers just get queued and eventually processed?
Yes
ok, so I’ll do that
Well if the workflow is just a counter, then there’s no issue with delays
it’s not just a counter
it does a bunch of other stuff
Ah yeah then there’s more consideration into it
can I call a workflow from another workflow?
like I could build a counter workflow and use it with workers set to 1 and always avoid the race that way
Yes but you’ll be charged one credit
For each invocation
ah ok
Just to let you know
But yes, that works