#jslaybaugh

1 messages · Page 1 of 1 (latest)

past tuskBOT
sleek thicket
#

Duplication can occasionally happen. Is this once in a while or for all/most events?

vocal trench
#

every time

sleek thicket
#

Can you share an example event ID?

vocal trench
#

evt_0MEFLCOc9qnPJL7OU7bVIVMO

#

I can see that there are two URL's under that event, but I don't know why... that first URL is for our connected platform. And then the second is also

sleek thicket
#

OK its because your test standard account is connected to your platform in live and test mode, plus you have the same endpoint url configured for Live+Test and COnnect+Account

vocal trench
#

Yes, but not the same events

sleek thicket
#

you should split up those endpoints in order to distinguish the events

sleek thicket
vocal trench
#

in the account, we only have 5 events filtered

#

and then for connected just 2

#

the only stuff we do for the connected accounts is this terminal stuff

sleek thicket
#

sure, ok, ignore the account endpoints (but still i suggest using a different URL)

vocal trench
sleek thicket
#

just within the connect endpoints, you have live and test using the same URL, same event types

vocal trench
#

why wouldn't I want that

#

I want live and test to all flow through the same code

#

and since this was a test transaction, it should just call the test endpoint

sleek thicket
#

So you can more easily distinsguish test and live events

vocal trench
#

ok, that's decent advice, but it still doesn't explain why a test transaction is triggering a test event AND a live event

sleek thicket
#

Yes, but in order to support some older integrations, connect events from live accounts using test mode Connect connections will send test mode events to both test and live mode endpoints, thats why you're seeing it twice

vocal trench
#

why would a test transaction trigger a live webhook

sleek thicket
#

So if you change your URL to eg use ?mode=live and ?mode=test eg

#

you could filter out the live one and discard it

sleek thicket
vocal trench
#

ok... so just to be clear, this only affects test mode connect connections

#

?

sleek thicket
#

It's test connections to live standard accounts -- that will also deliver test events you your live endpoints