hello! I have a question re: cloud pricing. one o...
# ask-community
m
hello! I have a question re: cloud pricing. one of the suggested solutions for sensor-type workflows is to have a task that raises a pause or retry signal (eg. as described at https://github.com/PrefectHQ/prefect/discussions/4156), and only progress to success when the task finds an appropriate file/event/whatever. am I right thinking that these retry+pause runs would not count as success for pricing purposes? So I’d only be paying when the polling task actually finds work to do?
k
You are right that only successful tasks are billed. Just don’t abuse it haha 😆
m
thanks! hopefully not planning anything crazy… just been evaluating Prefect vs some other tools and trying to estimate cost. I have some crons that would be candidates to transfer over, but they poll for new work every few minutes and in practice only find something a couple times per day. If I were to copy them into Prefect 1:1 I think there’d be a big difference between number of task runs vs actual work done
k
So in Prefect, our paradigm is that instead of polling, the event that happens can hit our GraphQL API and trigger a Flow
But polling in a task will definitely work
m
yeah, I think I’d want some combination of both depending on the exact use-case
k
Makes sense 👍
m
btw what’s the best way to schedule a call - fill out the contact form on the site? want to figure out whether this is a viable choice for us and we have a couple questions on pricing, enterprise, existing customers etc.
k
Yeah or you can email
<mailto:sales@prefect.io|sales@prefect.io>
m
nice - thanks!