This topic was automatically generated from Slack. You can find the original thread here.
Hi I want to deploy an automation, I haven’t used any credits. But my pipedream is telling me I have exceeded the daily credit limit. How is this possible? I made an automation to transcribe audio files. The audio file is in mp3 and it is less than 5 mb’s so it is easily doable for the automation.
You should visit https://pipedream.com/pricing for the latest pricing, but I’ll do my best to answer. It seems there might be a misunderstanding or an issue with the credit usage reporting. Credits in Pipedream are consumed by various actions within your workflows, such as steps executed in a workflow, invocations of sources, and compute time. Even if the audio file is small, the transcription process might be consuming more credits than expected, depending on the complexity of the workflow and the actions involved. To better assist you, could you provide more details about the workflow you’ve set up for transcribing audio files? Specifically, I would need to know: - The number of steps in your workflow. - The services or actions you’re using for transcription. - The frequency at which your workflow is triggered. This information will help me understand where the credits might be getting consumed and advise you accordingly. If you believe there has been an error, you can also reach out to Pipedream support directly at https://pipedream.com/support for a detailed review of your account’s credit usage.
Hi , would you mind accessing your Pipedream Billing and Usage page and share the screenshot of your Credit Usage section?
I see, could you share screenshot of the error you faced?
These are the details: Message:
You’ve exceeded your daily quota, see Limits
Total Duration:
0 ms
Compute Time:
0 ms
Execution Start:
Execution End:
null
Steps Executed:
0 / 5
Credits:
0
Version:
17 (d_n3sxd73J)
May I ask what is the error you faced in the event in your 2nd image?
That is this: “You’ve exceeded your daily quota, see Limits
Total Duration:
0 ms
Compute Time:
0 ms
Execution Start:
Execution End:
null
Steps Executed:
0 / 5
Credits:
0
Version:
17 (d_n3sxd73J)”
I don’t get wiser reading the daily credits limit page, because I didn’t exceed it haha
I see. I suspect that the workflow has consumed all of your credit. And the credit usage page has not been updated.
1 Credit is consumed for every 30 seconds of execution time, so if you workflow runs for a long time then it would cost quite a lot of credit.
In your workflow, have you tested running the whole workflow? How much time it consumed?
I haven’t I think
I have paused the workflow now, should I try again tomorrow?
In workflow Builder UI you can still test your workflow right?
Oops. Then I think you’ll need to try tomorrow. You can test the whole workflow in your Workflow Builder UI (which didn’t cost your credit) to get the total time of execution, from there you can calculate how much credit it would cost
You have this workflow configured to use a maximum memory allocation which is causing it to require more credits to run than you have available.
We charge 1 credit for 30 seconds of compute at the baseline 256mb memory allocation. Every 256mb increment costs an additional credit.
With the 10,240mb memory allocation you have set up, it will require 40 credits to execute.
Given the small file sizes, you should start with the base 256mb memory allocation.
