Describe the bug
When testing a "Finished Actor Run" Zapier trigger, the test step fails if the run's dataset is too large to download within Zapier's 30-second timeout. The timeout error is not handled gracefully and is propagated directly to the user.
To Reproduce
- Set up run with large dataset, e.g. Zillow Details Scraper (example https://console.apify.com/actors/ENK9p4RZHg0iVso52/runs/6oJarXPybAdEtQC4f)
- In Zapier, create a Zap using "Apify > Finished Actor Run" as the trigger, listening for the Zillow Details Scraper
- Run the test step in Zapier
- See error — no runs are pulled due to the dataset download timing out
Expected behavior
The 30-second timeout should be caught before it propagates to the user. Instead of showing an error, it should be logged as a warning internally, and the user should see a meaningful message.
Screenshots or video
https://www.loom.com/share/ed6aaf4a68f840fe80cee870dd92738e
Where was this bug reported
https://apify.slack.com/archives/C0L33UM7Z/p1773922704582759
Describe the bug
When testing a "Finished Actor Run" Zapier trigger, the test step fails if the run's dataset is too large to download within Zapier's 30-second timeout. The timeout error is not handled gracefully and is propagated directly to the user.
To Reproduce
Expected behavior
The 30-second timeout should be caught before it propagates to the user. Instead of showing an error, it should be logged as a warning internally, and the user should see a meaningful message.
Screenshots or video
https://www.loom.com/share/ed6aaf4a68f840fe80cee870dd92738e
Where was this bug reported
https://apify.slack.com/archives/C0L33UM7Z/p1773922704582759