This topic was automatically generated from Slack. You can find the original thread here.
i have a question regarding credits. it looks like my workflow is using more credits.the workflow has 5 steps. is every step consuming an credit ? in the event log i see 1 credit used. but it is consuming multiple credits. can someone explain ?
Of course, I’m here to help! Could you please provide more details about the issue you’re facing or the question you have? The more information you can provide, the better I can assist you.
explain credit usage in a workflow with 5 steps, and one trigger
You should visit https://pipedream.com/pricing for the latest pricing, but I’ll do my best to answer. In Pipedream, the number of steps in a workflow does not directly affect the credit usage. Most workflow executions use a single credit, regardless of the number of steps. This means that a workflow with 5 steps and one trigger would typically use one credit per execution, assuming the execution completes within 30 seconds at the default memory setting. However, if the execution time exceeds 30 seconds, or if you’ve increased the memory setting for the workflow, the credit usage could be higher. For example, if a workflow executes for 60 seconds, it would use 2 credits. Similarly, if you double the memory from the default 256MB to 512MB, it would also double the cost of credits for the same execution time. Please note that credits are not charged for workflows during development or testing. Also, using
$.flow.delay in a workflow will incur two credits: one for the initial start of the workflow, and another when the workflow resumes after the pause period. For more detailed information, please refer to the Pipedream Pricing page.
@U03CXTHK4RF not answering my question
I apologize for any confusion earlier. In Pipedream, typically, a workflow execution consumes one credit, regardless of the number of steps. However, there are certain conditions where more credits might be consumed: 1. If the execution time exceeds 30 seconds, additional credits are consumed. For example, a workflow that runs for 60 seconds would consume 2 credits. 2. If you’ve increased the memory setting for the workflow, it could also increase the credit usage. For instance, doubling the memory from the default 256MB to 512MB would double the cost of credits for the same execution time. 3. Using
$.flow.delay in a workflow will incur two credits: one for the initial start of the workflow, and another when the workflow resumes after the pause period. If you’re seeing multiple credits being consumed for a single workflow execution that doesn’t meet these conditions, it might be a good idea to reach out to Pipedream support for more specific help: https://pipedream.com/support.
, would you mind sharing how do you check your credit usage?
it consuming 1 by the workflow but credits increasing by 3
, could you access Pipedream Billing and Usage page? The page will show you details on your credit usage by resources
Well, I have to honestly tell you, as cool as the platform is, it’s just window dressing. I have to pay extra credits for discord receive notification and because the rcontent a rest api url changes. am very disappointed