Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I have a Zap that is supposed to copy new transcripts found in my Descript account to a Google Drive folder. It had been working for a while but recently I’ve been getting this error:

 

The full text of the error is:

id:

1d17f28d-ad3f-4c97-be57-cd0b46201149

succeeded:

true

audio_filename:

(Deleted for this post)

transcription:

hydrate|||.eJw9jcFuwyAMht-Fc5hIgJDktuOuU-8R2E6brYEIyLaqyruPdtFOtvz9_-c7g-Az-Tzm20psYK-sYrNP2XqgcUY2SKOlkEZVDLaUw7Ilik-gpNCtNhWzAGErhuPYal3C00xXHL1dHlKkr3GhfAlY7J_fNp4TG-7sePlPjmVglxtGm0NML2fKp2h9gjg7whP95JJzm8crPQ0HW_M7AZXx9qjXWJup6ZBblBNX0BvuSBsOKJxqG1HXqi-aNYYPgr-KUK4DUsQ7tMRVTcD7aXJcYDMp24BxEtm-779J2WH8:1pwqvU:M-2gisf7kJX-qkN0Xq9c5aV_t50|||hydrate

export__docx:

hydrate|||.eJxdUslu2zAQ_RWBpwQ1XUqipMi3HhqgQDekQU8FjNFwaLORSJakEhtB_72U7SZFeeEyb5mFzwydTWTTNh09sQ17x1bM2JjAIm2NYpu6a2pRd3LFcI7JTXOkcArIWjRt060YILo5K1we26bJYG1oVFsL0yKq6HE7Udo7ldUfniDsIts8s4vlS-Ry2LD9UQVILsT1jtL7g3chkbo1I2XQMFuVDws9gI0YjE93hJS3Dwu3VGWnqxvFQdWaS-w7PlDTcVRikG0lylL2WcYH95PwTBFyuEGSxG8UEJclIe-1HrhQlZZQYTfUS3o6J_D5XFAlqpqLhpeiKGteN1z2xZXfO0vXxXeDOXUDxZ07FldvyqISHe-rindN214XP-aq7Pv1JCFL0qm2Lz4ZZ08toUMeRsy3pWsOD0tXzMkSvB8NwoJ8-2jV2nmyh2nULkyQIndaG6RMmac8zfWTCyqXiBSjsbtpXP-NLKVDgOnkdia_WqVshU7RbaBfM1k8sk0rlv-A46zoE4QHCvcXTBbQMEZ6CX_NsrsAfv8PIoX5FfDNE2SBjzDQ-L_K72X9AZ4n2eA:1pwqvU:AI4NphxqUO625IHEtYO41NZ-Cso|||hydrate

export__srt:

hydrate|||.eJw9UctOwzAQ_JXIp1bUxc-4yY0DSFxA6oETUuTYm9bQ2JHjQKuKf8cJFb541zszO7u-IhN8Ap-adBkA1egBbZDzY9LeQOMsqrmSnHAlNshMYwr9NEJcCoITWUq1QdqYMGWF22MpZQZ3Dk628bqfRS18NT2kY7BZ_fNbx8OI6iu6tfyv3IIaHS826hTiuD1AejwPISawT-4EGdRO3uZgpkftRxPdkPZgIF_PM5daqjq2s1hb3mFhKoVbkAobS1pRMkKpqLLMEMMHmD8KEe3OgAC8sxqwoGBw1XUtJpZ1QjOjWj7b67KBl7-BGGEcE4kpKSjHXGJRFavhGDysizdnsnWni324FKs7WjCicMUYVrIs18X7xGhVbXuhsyQss70OyQW_rATO-TPGnOUmY0zzUtzSMeXK_XDSzs_mddT9gu9C7HW6gX_m8wv0tpJ7:1pwqvU:EuTLfCY43bzThGrq_-ct6cGp2H0|||hydrate

export__vtt:

hydrate|||.eJw9UctuwyAQ_BWLU6KGlKeJfeuhlXpppRx6qhRhWCe0MVgYp4mi_nuxE5ULu-zM7OxyRSb4BD7t0qUHVKMntELOD0l7AztnUc2V5IQrsUJmHFLoxgHiXBCcyFKqFdLGhDEr3B9LKTO4dXC0O6-7SdTCaddBOgSb1b9_dNwPqL6ie8v_yj2o0eFio04hDus9pOdzH2IC--KOkEHN6G0OJnrUfjDR9WkLBvL1OnGppaplG4u15S0WplK4AamwsaQRJSOUiirL9DF8gblRiGg2BgTgjdWABQWDq7ZtMLGsFZoZ1fDJXpsNvN0GYoRxTCSmpKAcc4lFVSz6Q_CwLD6cydadLrbhUiweaMGIwhVjWMmyXBafI6NVte6EzpIwz_beJxf8vBI4588YcpabnFKaluLmjilXHvujdn4yr6PuZnwbYqfTHfw7nT_17ZKF:1pwqvU:eg7R-0FPtM6P4ZSekLm-8VoeQC0|||hydrate

Fields with no value:

error

 

While requesting "dev_method" from Descript we ran into an error: You passed {raw: true} in request() - the response.content property is not available! Try response.body.pipe() for streaming, response.buffer() for a buffer, or response.text() for string.
 

Any help is appreciated!

Hi @SirCharles 

Good question.

I had a client encounter this error with GDrive.

Seems like it might have been a temp issue.

If all your Zap Runs are resulting in an error, then it’s work troubleshooting more.

Hi @Troy Tessalone , thanks for the comment.

Just to be clear, are you saying that this is likely an issue with Google Drive itself?

And when you say that it’s a temp issue, is that a specific type of issue, or are you saying that it was a temporary issue that’s theoretically been fixed or something?

All relevant Zaps are resulting in this error.

Ultimately, I got this explanation from the Zapier engineering team. If you’re getting a similar error with a different zap, the company you’re using might be using an outdated version of the Zapier platform as well. 

 

Hello Charles,
 
My name is Marley, from Zapier's Support Escalations team, and I'm happy to lend a hand!
 
My teammates and the engineering team took a deep dive into this case. We now know this is a very rare edge case that I'll try to explain below. Please bear with me as I try my best to explain the situation:
 

  1. There was an email that contained a dehydrated string (one of the ones that start with hydrate|||...) for the Descript integration -- As far as we can tell, the string was shared at some point by you with the Descript team when you were in touch with them about the issue. This was when the problem started with the "Sent Emails to Spreadsheet" Zap. 
  2. The Zap tried to "process" the string, which calls into the Descript app to get the transcript it points to. This calls an API on Descript's end, which returned a 500.
  3. The Zapier platform (used by our partners to develop their apps in Zapier, in this case, Descript) takes care of errors (like a "500" error) on its own. However, since it was meant to handle a stream of data (that of the dehydrated string), something went wrong with the content it was supposed to display. This caused the other unexpected error to pop up.

 
Upon further investigation, we realized that the Descript team is using an older version of the Zapier platform since the newer ones handle that edge case correctly.
 
The solution here would be for the Descript team to upgrade their Zapier platform to prevent this from happening again. We send comms every time that's necessary, but you could also ping them, taking advantage of the communication channel you've already established with them.
 
I hope this helps clarify things! 

 

@SirCharles 

Thanks for sharing the update.

Hi @Troy Tessalone I’m running into the same issue with Google Drive! When I am in testing mode, the file does get successfully created in dropbox, but the test step throws an error, saying

 

"Failed to create a file in Dropbox
While requesting "dev_method" from Dropbox we ran into an error: File/Folder not found”

 

How did you manage to resolve this?

Hi @Hello123

It is probably best to post your own topic and include screenshots of the encountered error along with how your Zap steps are outlined and configured.

Reply


Terms & Conditions