#skarmoryman_api
wild flickerBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1435325545016725690
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
floral geyser
Hi there
No that's not possible -- the created timestamp will always be set to the time that the object was created.
You can't modify that.
I'm not sure what you mean exactly by:
our system failed to pick up a dispute and upon further investigation it seems that the dispute records creation date was several minutes behind when it actually showed up on the api report
unkempt verge
To give you some context, our system checks for disputes using the created date between two dates. However it failed to pick up a dispute .
floral geyser
Is there a reason you don't rely on Webhooks here?
unkempt verge
And what I suspect is that the record appeared later than the creation date suggests
floral geyser
You are using the List API?
floral geyser
Gotcha, well no there really shouldn't be any reason that a dispute object would not appear within the created lte/gte if that is when the created timestamp is set to.
If you can reproduce then I'm happy to investigate, but otherwise I'm pretty skeptical that this was the root cause of the issue...
unkempt verge
When I call the api again with the exact same params I get a dispute back
Which is weird
So it seems like some kind of delay
floral geyser
You are seeing this regularly or it was a one off?
unkempt verge
Seems like a one off
So something else that leads me to to believe this is the issue is the fact that when I go on the console it says the dispute was received at 11:06
Which was several minutes behind the number on the api report
floral geyser
What do you mean exactly by "the console"? You mean the Stripe Dashboard?
And "the api report" is your own report based on using the List API?
floral geyser
Can you share the specific dispute ID
unkempt verge
Not right now as I don’t have authorization to share that
I’ll do some more digging
floral geyser
I'd recommend adding plenty of logging on your side around all of the relevant code to check if this happens again.
I'm really really skeptical this is an issue on the Stripe API side of things.
unkempt verge
We have a lot of logging and it says no disputes were found
I’m also surprised as I usually don’t have problems with stripe api
Definitley seems like a stripe issue as I’ve crossed referenced my original api calls from the stripe dashboard itself