This topic was automatically generated from Slack. You can find the original thread here.
Hi I have a workflow that is configured with 300 s timeout and 1024 mb memory(4credits) that is receiving 1 event everyday but it is taking 20credits or 24 credits everyday . What is the reason?
Hi I have a workflow that is configured with 300 s timeout and 1024 mb memory(4credits) that is receiving 1 event everyday but it is taking 20credits or 24 credits everyday . What is the reason?
It’s unusual for a workflow with 1024 MB memory (4 credits) and a 300-second timeout to consume 20 or 24 credits per day when it’s only receiving 1 event per day. There might be some factors causing this behavior, such as additional executions or longer run times. To better understand the issue, I would need more information about your workflow. Can you provide details on the steps within the workflow and their execution times? Additionally, please check the execution logs in the Pipedream UI to see if there are any unexpected executions or errors that might be causing the increased credit usage.
There are no unexpected executions or error events in inspector , however I am making use of a attachment and total number of steps in workflow are 14.
There are no unexpected executions or error events in inspector , however I am making use of a attachment and total number of steps in workflow are 14. The total execution time is 167,039ms
Based on the information you provided, your workflow has 14 steps and an execution time of 167,039 ms (approximately 167 seconds). With a memory configuration of 1024 MB, it should consume 4 credits per execution. However, you mentioned that it’s consuming 20 or 24 credits per day. One possible reason for the increased credit usage could be the attachment you’re using in the workflow. Large attachments might cause additional processing time or resource usage, which could lead to higher credit consumption. To further investigate this issue, I would recommend reviewing the attachment processing steps in your workflow and optimizing them if possible. If you’re still unable to identify the cause of the increased credit usage, please visit https://pipedream.com/support for more support options. Pipedream offers a range of community support options, and advanced customers get access to email and community support. Business customers get a dedicated account rep and a Slack channel with the Pipedream team.
Hi , the answer from Mario actually makes sense. Would you do as the answer recommended?
Hi the attachment that I am using is just 2349 bytes which is small so I don’t think it is the reason for extra credits , also how do I delete the attachment from workflow as I am not currently using that.
I think it’s quite weird. Maybe the Pipedream team can help to triage your issue when they’re available.
In the mean time, could you allow Pipedream support to access your workflow in your workflow settings, then share your workflow url here?
Hi Radhika, each 30-second block of compute time normally charges 1 credit. At 1GB of memory, each block is charged 4 credits. 167s of runtime = 6 30s blocks, multiplied by 4 = 24 credits. Let me know if that makes sense
Take a look at https://pipedream.com/docs/pricing/#credits for more detail
how did u calculate blocks from compute time ?
167 / 30, then we take the “ceiling” of that metric. e.g. 5.1 would be 6 blocks, since you’ve started the 6th “unit” of 30s compute time
The docs have a lot of good examples - take a look at that and let me know if that makes sense