@kaiser thanks - I'll update the question and probably post an answer once I figure out what precisely is causing the problem.

I just found out that I spent some 20000€ too much on behalf of my clients x_x So if you do not hear from me anymore, be sure to write me some nice letters to jail...

That sucks. :( Good luck sorting this out!

I don't think that this is a question for WPSE ;) But I could set a bounty on it to get answers :D

@fischi insurance?

@fischi wtf happened?

You are a freelancer, right? How come you are handling such amounts on behalf of a client with all risk on you?

Luckily, it is not all risk on me personally, as I registered an Austrian Limited 2 years ago. Nevertheless, now it is time to sort things out with clients. I hope most of them are as cool as the biggest one. Just got of the phone with him - and he just said, okay, let's shift the budgets, no problem.

I quit freelancing as my main business at the end of last year - now I just work for my company. Even more responsibility ;)

@kaiser some advertising budgets got out of hand, and a simple miscommunication between two servers created the problem - the receiving server allowed setting budgets to zero. but interpreted it as no input (false).

Oh so it isn't a single client but you spent too much money on a lot/all clients and it accumulates to 20000?

Yeah, exactly. Although the biggest accounts for nearly 10000.

That's a few months of worhtless work :D

Well then if they try to help you you're already halfway through, right?

wow that sucks

yeah, I hope so.

Looking back to the days where everything I worried about was some deadlines, not employees.

@fischi you automated too much? what exactly derailed in that server miscommunication?

@kaiser yeah, automated too much. I sent mutations for budget = 0, and got accepted request. at the latest update from the server, I still got accepted requests and no errors - but they handled the 0 as false, so did not change the value, and because I got no error showing up, I was not aware for some 5 days or so.

I know, it's not only their fault.

You didn't cast the result and handle it type safe, right?

Yeah, exactly. I didn't do double validation on the results.

Btw, what servers were you handling? Currently on the search for cloud hosting.

You mean my own? They're all at all-inkl.

The others? Mountain view...

What was your exact scenario if I might ask? all-inkl. API handling via Mountain view … ?

And what is "Mountain view"? Your Innsbruck bed room server next to the window? :D

Nope. My services run at all-inkl - dealing with the AdWords API servers from Google.

Got it.

Just a very bad feeling on a Monday at 8am. Realizing something did go wrong over the weekend, compiling data, and seeing the final result.

Actually, a bad feeling no matter what time it is.

This, right? developers.google.com/adwords/api/docs/appendix/…

Yeah, with all it's small nuances.

Sometimes Google throws Errors not even found by google itself, let alone the documentation. Sometimes there are Errors, but none thrown.

Then it wasn't really your fault. accountLimitType is a string.

;)

Just yesterday I was happy that fools like me work at Google.

No matter how big the name of the company - the guys working there are the same.

I know it's not just my fault.

One thing that I got forced on my head by stubborn mr. @gmazzap is bitwise operators. I'm glad I was forced to learn it as it makes it very safe to check and handle things in groups. Also, when you are used to it, it's nice and very clear to read.

I guess your lesson out of this is: Never automate budgets (yourself).

Yeah, I got a few things on my list to do better. Now that I realized how much is at stake. How much REAL money is at stake ;)

Enterprise budgets never are real budgets. That's one of the things that I had to learn.

However - now it is time to let my social skills do their part. Got to get this sorted (still am)

If I'm a fool, and fools work at Google, fools have responsibility for client's budgets too.

so there's going to be a way ;)

hehe