This topic was automatically generated from Slack. You can find the original thread here.
can you clarify how the custom event source cost works? Does the 1 credit for up to 30s run time apply if the source discards (as in not emit) the event?
Based on the information from the Pipedream documentation on Source Credit Usage, the cost associated with custom event sources operates as follows: - The initial free credit per execution only applies to sources from the Pipedream public registry that are attached to at least one workflow. This means that for publicly available components, the first 30 seconds of execution time do not count towards your credit usage. - For custom sources, which are not part of the Pipedream public registry, all computation time including the initial 30 seconds counts toward credits. This means that if a custom source runs, it will consume 1 credit for up to 30 seconds of run time, regardless of whether it emits an event or not. Therefore, if your custom event source discards the event (as in, it does not emit the event), it would still consume 1 credit for up to 30 seconds of run time. The key factor here is the execution of the source itself, not the emission of events. For more detailed information, please refer to the Pipedream pricing documentation.
alright I guess it makes more sense to use a raw unfiltered free source and then filter the events in the workflow it’s connected to then, since it’ll incur a cost anyway if it’s filtered through a custom source.
It seems like you’re considering the most cost-effective way to manage events in your Pipedream workflows. You’re correct in your understanding that using a raw, unfiltered free source and then applying filters within the workflow itself can be a more cost-efficient approach. This is because, as mentioned in the Pipedream pricing documentation, the execution of an event source is included for free when it triggers a workflow. This benefit applies specifically to sources from the Pipedream public registry that are attached to at least one workflow. Custom sources, on the other hand, would incur a cost after the initial free credit. Therefore, leveraging the built-in capabilities of workflows to filter events after they are emitted by a free source can help you optimize your usage of Pipedream credits. If you need to implement filtering logic within your workflow, you might consider using the Filter app to specify conditions that your workflow must meet to proceed or end execution. This approach allows you to manage event processing directly within your workflows without incurring additional costs associated with custom sources. If you have any further questions or need assistance with setting up your workflow with filtering logic, feel free to visit Pipedream support.