mathon

[polar wedge]

Hi, what do you mean by 'unexpected objects'?

[proven wagon]

Hey, I mean that our handling for webhooks like charge.succeeded is failing because we expect event.data.object.description to be on the json of the event

but event.data.object came as ""

[polar wedge]

Yes, that is. Thank you for flagging.

[proven wagon]

I think you get it, but just to make sure I'm clear:
{ "metadata": {}, "event": { "data": { "object": "", }, }
This is an object with the rest of keys omitted, object is "", but we expected to be {description: "string"}

[polar wedge]

That is correct

[toxic umbra]

Just to be super clear: events going directly to webhook endpoints should still be working as expected. However, if your webhook handling code does additional event retrieval at any point, or you're looking at this event at the dashboard we currently have an issue where you incorrectly get back object: "" when retrieving Events

[proven wagon]

We do fetch the event from the API. I was not aware of that, but found the code later

[toxic umbra]

👍 Yeah if you're doing event retrieval from the API then you're affected by the issue I mentioned earlier

[toxic umbra]

@proven wagon I think you saw this already but this should be resolved now!

[proven wagon]

@toxic umbra Thanks!