Glitch or Bug in n8n+Firecrawl Extract
Hey all. Really weird one here. My n8n workflow using Firecrawl Extract was working perfectly 2 days ago. Now, after using the Firecrawl EXTRACT node (and have tested this as HTTP Request node) , when the workflow then executes the next node, which is the Check Job Status Firecrawl node, it bizarrely changes the job ID which was passed as input from the EXTRACT node. Turns out it's weirdly triggering a new extract job in the previous node, and then using that new extract job id in the Check Job Status node. So the end result is that you can never check the status of the actual job id you started with. In short, when my Firecrawl/HTTP Request Check Job Status Node is triggered, its triggering the previous Firecrawl/HTTP Request EXTRACT node to resubmit the EXTRACT request to the API. I can go and check the results on my Firecrawl Account Overview on my webiste, but there is a bizarre glitch in n8n with the Check Status action. Has anybody had this happen to them? It's so weird!
