RE: account_budget 503 502:bad gateway,but in reality, it was successfully called

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

I will check with our team regarding your concern and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-08-20 10:31:03Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u4iop:ref" (ADR-00330459)

[苏子阔]

Any update on this? 

Or is there any solution for us to handle this request due to 502/503?

We need to verify whether the request was truly successful when we receive such errors. As a result, the internal system mistakenly identified the 5xx error as an operation failure and returned the amount to the customer.

I asked Gemini and he told me that it is possible to carry the same request_id to prevent duplicate requests, but after my research and testing, I found it invalid.

Thanks! 

Google Ads API Forum Advisor <ads...@forumsupport.google> 于2025年8月20日周三 18:31写道：

[Google Ads API Forum Advisor]

Hi,

We have an update for you, the 502: Bad Gateway error occurred due to some proxy server settings in our network connections. I would suggest verifying your budget status to see if it is in the expected status using the below query:

SELECT account_budget_proposal.account_budget, account_budget_proposal.id, account_budget_proposal.billing_setup, account_budget_proposal.status, account_budget_proposal.resource_name, account_budget_proposal.proposed_name, account_budget_proposal.proposal_type, account_budget_proposal.approval_date_time, billing_setup.status, billing_setup.id, billing_setup.payments_account, billing_setup.payments_account_info.payments_account_id, billing_setup.payments_account_info.payments_account_name, billing_setup.payments_account_info.payments_profile_name, customer.id FROM account_budget_proposal

You can try making a request using the Search or SearchStream by passing the customer Id. Also, you can use QueryBuilder to create your query and QueryValidator to validate your query. 

And retry the AccountBudgetProposal request, if you still experience the same issue provide the updated complete API logs (request and response logs with request-id and request header) generated at your end.

If you are using a client library and haven't enabled the logging yet, I would request you to enable logging for the specific client library that you are using. You can refer to the guides Java, .Net, PHP, Python, Ruby or Perl to enable logging at your end. For REST interface requests, you can enable logging via the curl command by using the -i flag.  

Also, it appears that you are using 'v19' of the Google Ads API. I would suggest to upgrade to the v21, of the which is the latest version of Google Ads API that enables you to use the new features introduced in each release and you may follow this link to Upgrade to the latest version.
 

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               

[2025-08-22 11:41:41Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u4iop:ref" (ADR-00330459)