Skip to main content
Best answer

Google Drive Error: 'Nonetype' object is not subscriptable

  • December 8, 2022
  • 10 replies
  • 524 views

In the last week or so I am suddenly getting lots of errors.  It has gone from automation to unreliable requiring constant monitoring.  No changes to my zaps.  Are others having this problem?

Best answer by jesse

Hey everyone! I am coming in here to let y’all know we have identified this as a bug. Our team is looking into this and it’s one of our top priorities right now. As we have updates, we’ll be posting them on this thread. I’ve also added each of you, individually to the bug report so that you’re notified personally as soon as things have been resolved.

We will be updating the main thread we have for this issue, here, when new information is available: 

I have closed this thread in the meantime. Thanks!

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

10 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34001 replies
  • December 8, 2022

Hi @Madeleine 

Can you provide more context about your Zaps?

Which apps are being used in the Zaps?

 

Check the Zapier Status page: https://status.zapier.com/

Check your Zap Runs: https://zapier.com/app/history/


  • Author
  • Beginner
  • 2 replies
  • December 8, 2022

Thanks.  I wrote it in Jan 2022 and it has run about 5 times a day since.  It triggers on a new attachment in Gmail, only continues if the email subject has a text match to a constant string and then saves the attachment on Google Drive.  Amid many normal runs, I get an error like this.  It has happened a few times in the last week and twice today.  It has run normally dozens of times.

  

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34001 replies
  • December 8, 2022

@Madeleine

For context, I’ve had other clients that have been experience issues with GDrive in Zaps lately so perhaps this is related.

 

I encourage you to open a ticket with Zapier Support to report this issue: https://zapier.com/app/get-help


  • Author
  • Beginner
  • 2 replies
  • December 9, 2022

Thank you.  Done.  The problem is worsening.  


  • New
  • 2 replies
  • December 9, 2022

In the last week or so I am suddenly getting lots of errors.  It has gone from automation to unreliable requiring constant monitoring.  No changes to my zaps.  Are others having this problem?

yes same problem!


  • New
  • 2 replies
  • December 9, 2022

@Madeleine

For context, I’ve had other clients that have been experience issues with GDrive in Zaps lately so perhaps this is related.

 

I encourage you to open a ticket with Zapier Support to report this issue: https://zapier.com/app/get-help

that’s what I did, byt never received a reply. Still waiting.


  • New
  • 2 replies
  • December 9, 2022

Same for me. Today I got a zap that should have ran 2 times but it never ran so my customers needs manual help. Tedious asf


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34001 replies
  • December 9, 2022

Hi @hanman 

Check the Zapier Status page for current/past incidents: https://status.zapier.com/#incidents-list


  • New
  • 2 replies
  • December 9, 2022

Hi @hanman 

Check the Zapier Status page for current/past incidents: https://status.zapier.com/#incidents-list

Thank you! Seems like it was just a delay. The zaps ran now.


jesse
Forum|alt.badge.img+9
  • Architect
  • 1348 replies
  • Answer
  • December 9, 2022

Hey everyone! I am coming in here to let y’all know we have identified this as a bug. Our team is looking into this and it’s one of our top priorities right now. As we have updates, we’ll be posting them on this thread. I’ve also added each of you, individually to the bug report so that you’re notified personally as soon as things have been resolved.

We will be updating the main thread we have for this issue, here, when new information is available: 

I have closed this thread in the meantime. Thanks!