This topic was automatically generated from Slack. You can find the original thread here.
Analytics Admin : Hi there … is there a way to set limits so I don’t accidentally rack up a huge bill? I have signed up for the pro plan.
This topic was automatically generated from Slack. You can find the original thread here.
Analytics Admin : Hi there … is there a way to set limits so I don’t accidentally rack up a huge bill? I have signed up for the pro plan.
Dylan Sather (Pipedream) : Hi , I totally hear you on the use case. For now setting direct limits isn’t possible, but we’re tracking that request here.
We do return the number of invocations used in your current billing period from the /users/me
REST API endpoint:
{
"data": {
"username": "dylburger",
"email": "[dylan@pipedream.com](mailto:dylan@pipedream.com)",
"billing_period_start_ts": 1610154978,
"billing_period_end_ts": 1612833378,
"billing_period_invocations": 12345
}
}
You could develop a workflow that runs once an hour (for example) that polls this endpoint and emails you if you hit some threshold.
Then you can see the (day, workflow)-level breakout of invocations in your billing settings to figure out which resource is responsible for the usage.
Let me know if that helps for now, and feel free to follow that issue for updates!
Analytics Admin : Thanks
THe biggest thing I’m worried aboiut is one of my devs writing some code that goes crazy and just blows up my billing.
Analytics Admin : I know google’s cloud platform has such a feature.
Analytics Admin : The free plan protects me so would make sense that I could set some limit similar to the way the free plan sets it’s limit.
Dylan Sather (Pipedream) : I hear you 100%
Dylan Sather (Pipedream) : if you follow that issue, you’ll get updates as soon as we have them
Analytics Admin : Great thanks
Analytics Admin : Any eta on it / where it is in the line of proiorities?
Analytics Admin : Just curious how y’all handle that
Dylan Sather (Pipedream) : It’s not on our immediate backlog, so I don’t have an ETA, but we frequently evaluate priority based on feedback from customers, and I shared all of this with the team.
David Watson : I’m still in development mode, so my usage is currently limited but I will have similar concerns when I switch over production for my apps, so this information was very valuable to me.