• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Apify workflow with delay showing errors

Lawyal

Member
Your Task History ID
IjU3NjUwNTY5MDYzZjA0MzI1MjY5NTUzYzUxM2E1MTYyNTQzMjBmMzYi_pc
Hello,
I set up multiple workflows that receive a TikTok video URL as trigger (by mail or RSS). The URL is sent to Apify for download and then converted with Cloudconvert.

This workflow worked well for over a week in over 40 runs: "Apify: Custom API request" is pulling the video, then a 5 min. delay, then the "Apify: get dataset items" is pulling the data. This step is now is always throwing an error:
error Type: page-not-found
error Message: We Have Bad News: There Is No API Endpoint At This URL. Did You Specify It Correctly?

We tried to extend the delay but this didn't help.

The workflow automatically re-executes after some time which fixes the error that the Apify step was showing, but the re-execute is throwing some new errors in the next steps (missing data and so on). So I need to find a way to get the Apify step working again.
I checked with Apify but the data download is working well, no errors on their end.

Further investigation shows that the problem seems to be in Pabbly itself, specifically related to using delays.
I'm not sure why its creeping up now since it worked in all the previous days, maybe you guys changed something internally?

Thank you for your help


apify_p1.jpg


apify.jpg
 

Preeti Paryani

Well-known member
Staff member
Hello @Lawyal,

It appears that the task history has been re-executed and is now working as expected.

1750328626710.png


Please feel free to reach out if you encounter any further issues. We’ll be happy to assist you.
 

Lawyal

Member
Hi @Preeti Paryani
you are correct, in all workflows that use these steps, they automatically re-execute after some time.

This solves the Apify problem (although I get a mail for the error) but leads to another problem at the end, where the Nifty task is created. This step fails, if the workflow re-executes automatically (the document link is not attached to the Nifty task).

I'm looking for a solution that the "Apify: get dataset items" step does not fail in the first try (on all workflows). The error still exists.
It worked for 1 week without problems and for the last 2 days it always fails.
 

Preeti Paryani

Well-known member
Staff member
Hello @Lawyal,

Thank you for sharing the details.

To help us investigate further, please share the workflow URL where you are experiencing the issue. Additionally, kindly set the auto-re-execution settings for the same workflow to "Disable", number of attempts to zero, so that we can review the errors as they occur.

1750336399447.png


Looking forward to your response.
 
Top