Yann_Lair

Thank you, we will try to push our investigation further, somehow.

That is the custom log that we have on our code to display each object that gets sent to CustomObject. This log stores it in the cloudwatch log for that particular lambda.

Hi,This is happening in a lambda function from AWS, so what you see is the object in the serialization of the object that gets sent through the in the marketo API client as we log it and retrieve through cloudwatch. Unless there is tools on Marketo sides that would allows us to look at what's coming...

That feels like that it should be written down in there doc! I would have saves days of work trying to figure out what was wrong on our side when it was just the marketo architecture working as intended but without anybody knowing. I'm pretty sure I won't be the only one bamboozled by the successfu...

Done!Is this async architecture mentioned in the API doco? I've read it and I can't remember seeing this. If I missed it, other will too. Can you point where we can read more about that in the doco? That'll probably help future people to get that info. Thanks mate.

Thank you for your time, it is much appreciated. I understand better the constraints linked to the marketo architecture and how to handle it properly forward. Thanks again for the quick answer!

Thank you for your quick answer. I understand your point about the request being idempotent, I might have not express myself clearly. What I was meaning to say is that I would expect the same call in the same situation to give me the same answer. In this situation, you make a first call, its returns...