Failed due to authentication errors ?

[Christopher Larkin]

Hi -

I am recreating the script which no longer works and I am not receiving a prompt to access the Google Sheets doc. 

Is there a bug in the environment right now? 

Unchanged, existing copies of my scripts run but when I make any changes, or if I create a new script, I never get the request for authorization to access the Google Sheets doc that stores my output.

Thanks in advance -

Chris

[Christopher Larkin]

Hi all -

Here's a workaround. It's a REALLY SILLY workaround, but if you have this problem about authentication, here's a simple fix I figured out. 

Go to a script that works right now, then select the drop-down and choose "Duplicate" -- once the copy appears, you'll need to click to authenticate and give the script permission to run. 

Now you can completely edit (even replace!) the main code and preview/save then schedule. 

It makes no sense that I can't just make a new script (that would cause the "failed due to authentication error" message). 

Hope this can be duplicated at Google and fixed. 

Thanks!

[Google Ads Scripts Forum Advisor]

Hi Chris,

Thanks for posting your concern and sharing the workaround that you've used to address this.

You are correct that creating a copy of existing scripts is the possible workaround so that the new scripts will perform similar task with the old one. However, please let me discuss this with our team and will share information to this thread once available.

Regards,
Ejay
Google Ads Scripts Team

ref:_00D1U1174p._5001UV0fvO:ref

[Christopher Larkin]

Hey Ejay -

Please do once I save the copy I cant edit it later either.

[Josh Mason]

Logging in incognito mode seems to work as well... just fyI. Having a similar issue when setting up scripts in new accounts.

[Christopher Larkin]

Somehow it's working for the accounts I couldn't add scripts to the other day. 

I hope it's resolved for everyone. 

[Google Ads Scripts Forum Advisor]

Hi everyone,

Our team is currently investigating the issue and we'll provide updates via this thread once available.

For now, you may try the workaround of creating a copy of existing scripts should the issues persist.

Thanks,
Peter

[Róbert Lelkes]

Can't be applied if you have no running scripts, but Incognito works for that (at least for me it worked for now). Thanks for the updates :)

[Louise Snel - FindFactory]

Unfortunately the work-around you mentioned doesn't work for me. Also the incognito doesn't work. Is Google allready working on a fix? Two years ago the same thing happened!

Op donderdag 13 februari 2020 00:52:06 UTC+1 schreef Christopher Larkin:

[Google Ads Scripts Forum Advisor]

Hi Louise,

We are currently addressing the issue -- your patience is very much appreciated.

Thanks,
Matt

[Roy Steves]

I've tried clearing cache and cookies, as well.  

It doesn't seem tied to a specific user account, either--my entire team is hitting this error, with increasing frequency today.  We also cannot set schedules for affected scripts.

This is a massive disruption for us, Matt, so any update you can give us would help us prioritize our triage efforts.

[Google Ads Scripts Forum Advisor]

Hi Roy,

Thanks for your patience on this. This is being worked out internally at the moment. I will provide an update ASAP on this.

[Yoann Berthome]

Hello there

And could you at the same time explain why the ownership of script changed to Your Google Account Team for some scripts ?

Could we have an estimation of when the issue will be solved... it's a huge issue now.

Kindly

[Google Ads Scripts Forum Advisor]

Hi Yoann,

We are currently working on a fix for this. It appears to only be a UI issue at the moment. We appreciate your patience as we continue to address the issue.

[Yoann Berthome]

Hello,

The issue is weird, and really random

Yesterday I created a new script, copied all from the script that had issue.

it was working

this morning, I updated the code, and try a preview, issue shown..

I ll PM you CID and script name.

[Google Ads Scripts Forum Advisor]

Hi Yoann,

Thanks for providing the customer ID and the name of the script privately.

Technically, an existing script could not be updated. So, even after creating a duplicate script the issue will occur if you modified it after the first authorization. With this, I recommend that you create a duplicate of the script and before you authorize it, you may apply all the changes first as a workaround.

However, my apologies as well as our team cannot further comment about the existing issue at this moment. Our team is currently working on the issue and we shall provide more information via this thread once available.

Best regards,
Peter
Google Ads Scripts Team

ref:_00D1U1174p._5001UV0fvO:ref

[Finn Harnett O'Meara]

Hi Peter,

Is there any update on this? 

Thanks,

Finn

[Google Ads Scripts Forum Advisor]

Hi Finn,

I have requested an update on this -- as soon as I hear back, I will relay this information to you. Your patience is appreciated on this.

Thanks,
Matt 

Google Ads Scripts Team

ref:_00D1U1174p._5001UV0fvO:ref

[Roy Steves]

We're seeing fewer (but not none) instances of this bug.  While I understand you've already requested an update, since it's been a week and a half, maybe it's time to rattle the cage again?

[BI ABlab]

Hi Guys,

Are we supposed to be on this tread? We are a marketing agency.

Cheers,

Hugo

--
-- You received this message because you are subscribed to the Google Groups AdWords Scripts Forum group. Please do not reply to this email. To post to this group or unsubscribe please visit https://developers.google.com/adwords/scripts/community.
---
You received this message because you are subscribed to the Google Groups "Google Ads Scripts Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adwords-scrip...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-scripts/4c1bc451-a763-47d0-9675-594e1dead086%40googlegroups.com.

[Google Ads Scripts Forum Advisor]

Hi Roy,

Thanks for reporting this. I will check the current status of this issue and report back on this thread.