• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

How to rerun a Google Docs document creation step when it returns "Internal Error?"

JeffreyYu

Member
Your Task History ID
IjU3NmQwNTZjMDYzNzA0MzA1MjZkNTUzNjUxMzQ1MTY3NTQzMCI_3D_pc
Hi Pabbly,

I'm wondering how I can rerun a Google Docs document creation step when it returns a internal error. I've attached a screenshot of this below. The problem is that the step returns Success when it should return Failure, so Pabbly's automatic re-execution for failed steps doesn't work here.

Since I have 8 of these steps, it seems like a hassle to create another Router after this step runs, testing if an error code was returned. After all, what if Google Docs is just down for a few seconds, enough where any immediately following Google Docs step run also return an internal error?

I'm wondering thus if Pabbly could return Failure for these situations, so that the automatic re-execution gets fired. Thank you!

Jeff

1719072728052.png
 
P

Pabblymember11

Guest
Hey @JeffreyYu

Apologies for the delay. Resolving this issue may take some time, but rest assured, we will inform you as soon as there is an update from the technical team.
 

JeffreyYu

Member
Hello! I'm following up on this thread. Today, I got a similar error from Pabbly Connect (pasted below). How can I set up Pabbly Connect to catch these errors?

Here is the task ID: IjU3NjUwNTZkMDYzNTA0M2Q1MjY1NTUzMTUxMzA1MTZiNTQzMjBmMzIi_pc

Code:
<!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 502 (Server Error)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>502.</b> <ins>That’s an error.</ins> <p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
 

Preeti Paryani

Well-known member
Staff member
Hello @JeffreyYu

It seems to be a temporary error from the Google Docs API's end. If you want this task history to get executed you can go to the history and filter using the concerned task history ID then click on the task history ID > click the Re-execute dropdown > Select Entire workflow.

image-09-26-2024_04_01_PM.png
 

JeffreyYu

Member
Hello! Yes, I'm aware I can re-execute the task history. My question though is, how can we have Pabbly Connect detect if this particular response is returned, and mark it as an error? Pabbly marks it as a successful execution even though the message says its an error. Thus, the only way I've learned these errors exist is because our staff have been saying that the google docs sometimes haven't been created successfully.
 

Preeti Paryani

Well-known member
Staff member
Hello @JeffreyYu

We have escalated your concern to our technical team, kindly allow us some time to work on this and we will update you as soon as we make any progress.
 
Last edited:

JeffreyYu

Member
Hello, following up on this thread! I know the best long term solution would be to catch this type of response and then treat it as a Pabbly re-execution error.

However, I'm wondering if there's any temporary solution I can put in place instead for now? I considered putting a Router, but the issue with that is that if the first iteration fails, then there would only be one opportunity for a re-running of the function call. And if the second function call fails, then there's no way I would know since it's marked as a success.

Is there any way in Pabbly connect to manually throw an Exception if, say, the google doc step doesn't return a "Text Replaced" or specific output? That way, I could be notified and then manually go in and re-run it.
 

Preeti Paryani

Well-known member
Staff member
How @JeffreyYu

You can add a router to filter if the Google Doc step throws an error and add a subsequent Gmail step to send a mail to your Email ID regarding the error. In this way, you will notified and then can re-execute it manually.
 

JeffreyYu

Member
That's the thing though -- when this error message happens, it DOESN'T throw an error. And also, the router approach I mentioned above has the aforementioned flaw / lack of scalability.

1727945682916.png
 

Preeti Paryani

Well-known member
Staff member
Hello @JeffreyYu

Our team has made some changes to capture the server errors in Google Docs as errors in Pabbly Connect. Can you please check it at your end if it's working fine for you?
 

JeffreyYu

Member
Thank you so much Preeti! It's a little tough to replicate the error since it's so sporadic, but I will keep an eye out on whether my staff encounter issues with Google Docs in the next few weeks. If they don't, then this issue is fixed!
 
Top