• 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

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

Google Drive 10 min trigger time

nickurban

Member
Hi,

I setup an automation to notify Slack every time a new file with the word "-Intro" is uploaded to a Shared Google Drive folder. Pabbly says the trigger time interval is 10 minutes.

I've been checking slack for the last 25 and still nothing. Test Request worked fine. I checked Workflow History, and there's been no update/run for 25 minutes. Why?

Thanks for the help.
 

nickurban

Member
Correct. It was triggered shortly after I made the workflow. It has now been over 90 minutes and, according to Workflow History, has not run a single time since then. As you can see, all 91 instances ran at 16:39:39.

Also, to be clear, I chose "New File In Specific Folder (Shared Drive)". The 91 items are almost entirely folders, not files. The files titled things like "186-Intro.test" should pass the filter criteria which is simply Name of "New File in Specific Folder (Shared Drive)" Contains "-Intro".

Why didn't this Task succeed?

IjU3NjUwNTZjMDYzNDA0M2M1MjZlNTUzNDUxMzA1MTZhNTQzMDBmMzMi_pc

UPDATE: Seems that the test files were empty and that was the issue. Although they showed in Drive, they didn't work with Pabbly. I also noticed that the interval was actually 20 minutes, not 10 for the test files I used.
 
Last edited:

Preeti Paryani

Well-known member
Staff member
Hello @nickurban

Your workflow seems to be triggered after the mentioned time, refer to the attached image.
It has now been over 90 minutes and, according to Workflow History, has not run a single time since then. As you can see, all 91 instances ran at 16:39:39.

1732081883774.png


Also, regarding the issue related to the provided task history we have made a change in the filter step(removed the '-' from the value), refer to the attached image. Then we have re-executed the provided task-history and it successfully got re-executed.

Task History ID after re-execution: IjU3NjUwNTZjMDYzNDA0M2M1MjZiNTUzMTUxMzA1MTZhNTQzMTBmMzMi_pc
IjU3NjUwNTZjMDYzNDA0M2M1MjZlNTUzNDUxMzA1MTZhNTQzMDBmMzMi_pc
1732082122546.png
1732082128006.png


Please note that the trigger will get triggered if any folder or file gets added to the specific folder, to proceed with the further steps only if the captured detail is not a folder you can add a filter as per the below attached screenshot.
I chose "New File In Specific Folder (Shared Drive)". The 91 items are almost entirely folders, not files.

1732082438523.png


Also, please note that if anu file gets captured on clcik of "Save and Send Test Request" button, it will not be captured under the task history.
 
Top