Stopped due to timeout

[Mat]

The script that used to work perfectly fine across many Google Ads accounts has had some problems from today. It has started to work much longer and triggering a "stopped due to timeout" errors.

There were no changes in the code.

Because there is still a lot of bugs in the Google Ads interface (no logs data, no possibility to set the MCC account as the owner of the script in the filter) it is impossible to me to find a source of the problem or the solution.

[Google Ads Scripts Forum Advisor]

Hello Mat,

I’m James from the Google Ads scripts support team. Thank you for reaching out to us.

Could you please provide us with the following information below so that we can further investigate?

• Google Ads account ID / CID
• Script name
• On what version are you running the said script (Legacy or New Scripts experience) when you experience the timeouts?

Regards,

James Howell Google Ads Scripts Team

ref:_00D1U1174p._5004Q2eOIui:ref

[Liana Smit]

Hi brother can you share the script ?

ср, 14 сент. 2022 г. в 13:27, Mat przez Google Ads Scripts Forum <adwords...@googlegroups.com>:

The script that used to work perfectly fine across many Google Ads accounts has had some problems from today. It has started to work much longer and triggering a "stopped due to timeout" errors.

There were no changes in the code.

Because there is still a lot of bugs in the Google Ads interface (no logs data, no possibility to set the MCC account as the owner of the script in the filter) it is impossible to me to find a source of the problem or the solution.

--
-- 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/9682abd9-4ff8-49ec-a2f8-2ecf20c930e1n%40googlegroups.com.

[Mat]

It looks like it was a one-day problem. If it doesn't happen again, I don't think there is any need for further investigation.

[Mat]

But of course it is still worth working on the other bugs I mentioned:

"Because there is still a lot of bugs in the Google Ads interface (no logs data, no possibility to set the MCC account as the owner of the script in the filter) it is impossible to me to find a source of the problem or the solution."

[Google Ads Scripts Forum Advisor]

Hi Mat,

 

This is Yasmin from the Google Ads scripts team. Thank you for confirming that the issue appears to be fixed on your end, as well as providing your insights.

 

However, for us to further investigate the observations from your statement, "Because there is still a lot of bugs in the Google Ads interface (no logs data, no possibility to set the MCC account as the owner of the script in the filter)", we would be needing the information my colleague, James, requested from you. Would you be so kind as to provide them?:

• Google Ads account ID / CID
• Script name

• Screenshot of the issues
• On what version are you running the said script (Legacy or New Scripts experience) when you encountered these errors?

 

Kindly send the requested items via `Reply privately to author` option. If the said option is not available on your end, you may send those through the email alias `googleadsscr...@google.com` instead.

 

Regards,

 

 

Yasmin Gabrielle Google Ads Scripts Team

ref:_00D1U1174p._5004Q2eOIui:ref