Hello,
It's been quite some time since our last communication regarding the LSA
call recording issue. We are still encountering 500 responses when
accessing call recordings.
I noticed that version 17 of your API has been released. However, there is
no mention in the release notes about whether
Hello,
I haven't heard anything yet. I'm reaching out again for any updates, and I'll
let you know when I get any information I can share.
This message is in relation to case "ref:!00D1U01174p.!5004Q02s01O1:ref"
(ADR-00227692)
Thanks,
Michael Cloonan
Google Ads API Team
--
--
=~=~=~=~=~=~=~
Hello,
I'm writing to see if there are any updates on the matter we discussed
regarding the LSA call recording issue.
Your assistance is greatly appreciated.
On Saturday, May 11, 2024 at 7:54:55 AM UTC+8 Julius Decena wrote:
> Hello,
>
> Thank you for getting back to me. I appreciate your assi
Hello,
Thank you for getting back to me. I appreciate your assistance on this
matter. Looking forward to your response once you have more information.
On Fri, May 10, 2024 at 8:05 PM Google Ads API Forum Advisor
wrote:
> Hello,
>
> I'm checking with the team on the status of this fix. I know it
Hello,
I'm checking with the team on the status of this fix. I know it was planned for
v16_1 but it's not clear whether it actually made that release. I'll let you
know when I find out.
Also, for additive minor releases like v16_1, the API version remains v16 for
actual requests and other impo
Hello,
I hope this email finds you well. I wanted to bring to your attention that
API version 16.1 has been released. However, upon reviewing the release
notes, I didn't find any mention of the LSA Call Recording 500 response
issue being addressed.
Additionally, I conducted some tests and foun
Hello,
That's good to hear, I appreciate your help on this matter.
On Tue, Apr 9, 2024 at 2:11 AM Google Ads API Forum Advisor
wrote:
> Hello,
>
> They got back to me already. Apparently, to fix this issue we need to wait
> for the next release of the API, which will be v16_1. You should follow
Hello,
I wanted to follow up again on the ongoing issue we discussed regarding the
500 errors we've encountered with some of the LSA lead call recording URLs.
I appreciate your effort in monitoring the progress. As it has been some
time since our last communication, I wanted to inquire if there h
Hello again,
Just following up on this and would like to know if there has been any
update regarding this matter. Thank you
On Wed, Mar 20, 2024 at 9:26 PM Julius Decena
wrote:
> Hello,
>
> I appreciate your assistance in this matter, look forward to hearing from
> you.
>
> On Wed, Mar 20, 2024
Hello,
I appreciate your assistance in this matter, look forward to hearing from
you.
On Wed, Mar 20, 2024 at 8:50 PM Google Ads API Forum Advisor
wrote:
> Hello,
>
> Thank you. I've passed this information along so that someone who knows
> about this feature specifically can take a look. I wil
Hello,
Thank you. I've passed this information along so that someone who knows about
this feature specifically can take a look. I will keep an eye on their progress
and let you know as soon as I have any new information to share.
This message is in relation to case "ref:!00D1U01174p.!5004Q02s01
Hello,
Here's a new set of LSA lead recording URLs with their respective customer
ID, the 500 internal server error seems to be happening frequently:
- 8058690966 -
https://ads.google.com/localservicesads/attachment/CJPqhVwQn_S-7AsYsonwjgEyA2doczgC
- 5765044803 -
https://ads.goog
Hello,
Thank you for this context. I think I finally understand what's going on here.
You provided a few URLs previously that were failing. Can you provide me with
the corresponding customer ID for each of those URLs (since you said that they
were from a variety) so that I can pass the informat
Hello,
Yes, I am using Google Ads API. The URLs I provided are call recording URL
from this query:
SELECT
local_services_lead_conversation.phone_call_details.call_recording_url
FROM
local_services_lead_conversation
On Wed, Mar 20, 2024 at 1:23 AM Google Ads API Forum Advisor
wrote:
> H
Hello,
Are you using the Google Ads API for this? My team is only able to provide
support for the Google Ads API specifically (generally troubleshooting errors
with specific requests/responses to the API).
If your query is about a Google Ads feature in general, not specific to the
API, you can
Hi Michael,
I appreciate your assistance on this matter. Here are some sample recording
URLs that results in a 500 or internal server error response:
-
https://ads.google.com/localservicesads/attachment/CPHPw18Qk9SW8QsYtd_ejgEyA2doczgC
-
https://ads.google.com/localservicesads/attac
Hello,
This case has been escalated to me.
Can you provide a specific example request/response where you get this error,
or at least a request ID for a request where you got this error, so I can take
a look at our logs and try to see if I can find any more details about what
caused the interna
Hello,
I understand that an 'INTERNAL_ERROR' could be transient in nature, but it
doesn't appear to be the case here. We're able to retrieve other call
recordings fine, but not the others.
Here's one instance:
- 2307495627
- creationDateTime: 2024-03-05 12:54:19.236424
- We've tried s
Good day,
We've recently integrated LSA call recordings into our system. We've
noticed that we're receiving 500 Internal Server Error responses for some
of the LSA call recording URLs. Could you please confirm if this is an
expected response for these URLs, or if there might be something happen
19 matches
Mail list logo
