PipedreamHQ / PipedreamHQ/pipedream
Firecrawl
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
### App
Firecrawl
### Summary:
Firecrawl credits depleted by 116 failed scrape requests returning Invalid Date
### Details:
One of our users connected Firecrawl through Pipedream. Immediately after the connection, approximately 1,000 Firecrawl credits were consumed in about 13 minutes. Firecrawl recorded 116 scrape requests, and all of them failed with "Invalid Date" errors.
Please pull the activity / tool-call logs for this connection during that window and share the exact invocations, request timestamps, input payloads, retry behavior, and any error details so we can identify what triggered the calls and why credits were consumed. The user's Firecrawl quota is now fully drained.
Related community thread: https://pipedream.com/community/t/why-did-the-firecrawl-credits-get-used-up-rapidly-through-the-pipedream-connector-resulting-in-116-failed-scrape-requests/14457
I can provide the exact connection or user details privately if required.
### Screenshots:
No screenshots included
Contributor guide
Research direction
Review the activity and tool-call logs for the affected connection during the reported 13-minute window, using the linked community thread for context. Done means documenting the exact invocations, timestamps, input payloads, retry behavior, and error details, and identifying why the failed requests consumed credits.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100