1/ time for a little bit of a bragging thread
-
-
10/ ...Given that in your documentation Error Code 411 always means "no inventory", and your system should assume that the order attempt failed, it is my belief that we responded correctly and your system is in error. Please advise.
Show this thread -
11/ P.S. The unique identifier ID in your message was XYZ and our response was QRS.
Show this thread -
-
13/ I'm reminded of two stories from when I was first dating
@LibertyFarmNH. One time we were out on a date, and the truck didn't start (turns out alternated died). She said "oh no!". I shrugged, went to the cargo area, got the [ charged ] jumper pack, and started the truck.Show this thread -
14/ Another time we were exploring rural areas, the paved road turned into a dirt road, and the dirt road got ruts, and we hit something with a BANG and then we heard the muffler dragging on the ground I stopped, got the tool kit, removed a broken bracket, and used bailing wire
Show this thread -
15/ You can predict 99% of the problems that are going to happen, and plan ahead to mitigate them.
Show this thread -
16/ Counterpoint to
@FormerlyFormer 's "male strengths vs female strengths" threads: youth strengths vs elder strengthsShow this thread -
Show this thread
-
18/ BigCo responded. "I looked in our system; I see our message to you, placing the order. Problem at your end." ok, BigCo, can you tell me what order ID # we gave you, and what our message said specifically? "there was no order ID. Your response was 'error: no inventory' "pic.twitter.com/V9tkGlGvUp
Show this thread -
-
20/ wife responds to my email above ("Woman! Fetch my excruciator!")pic.twitter.com/mW7EwxYDpc
Show this thread -
21/ me: can you confirm that you ignore the message we send back to you, even if we specify a well defined error code, as documented in your API ? Bigco: <2000> words me: ok, so you do ignore the error code. Alright, I'll dig into the other API now.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.