Firecrawl scrape requests sometimes don’t register, leaving my workflow stuck in a status loop

[sen]

I’m using Firecrawl to scrape a real estate website every week. There are 9 suburbs in total, and my workflow scrapes them one by one, adding the data to the relevant Google Sheet.

The issue I’m running into is that sometimes the workflow gets stuck in the “checking status + wait” loop. This happens because, even though the request was sent, Firecrawl never actually receives it — so the status never updates and the loop runs indefinitely.

My current idea is to only let the loop run a maximum of four times. If the status still hasn’t updated after that, I want the workflow to re-send the extract request to Firecrawl.

How would I set this up? Or is there a better approach to handle this situation that I should consider?

---

[moosa]

or before wait here:

you can check id status of request.
200 or 400 or 500 and handle it before checking
as the issue you are facing

@sen

Firecrawl never actually receives it — so the status never updates and the loop runs indefinitely.

[sen]

Hey thanks a lot for the reply!
Unfortunately it does not give an error message. For the status it simply just says processing.

[moosa]

could you share results from both scenarios?
a. never ending loop
b. normal execution

[sen]

The above two are the results for the extract property info node. Where run 9 is the one resulting in the infinite loop.

The above two are for checking the status node.