jumpinj_api

[brave prawn]

👋 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/1445800170439835819

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[strong mantle]

Can you share an invoice id you expected to be returned for each of those requests

[brazen seal]

Yes I expect it to return in_1SZuGZLZ5PeoRLWoI9KxcAYS

[strong mantle]

Oh

The created is the actual created timestamp reflected on the invoice

Not the test clock created time

[brazen seal]

Hmm that is unfortunate. Is that intended behavior in Stripe or a bug?

[strong mantle]

Looking into that rn

I'm actually not sure offhand

I do know there's various expected issues with filtering for test clock invoices

[brazen seal]

Thank you, I would love to see that use the timeclock timestamp. Ya some of those are mentioned in the Stripe docs in this section, but I don't see anything about created field in it. If not going to be changed could the docs get updated to reflect this behavior?

[strong mantle]

Ah ok I found a report of this internally

It's backlogged to be fixed but hasn't been prioritized unfortunately since it's something that only affects the test environment

[brazen seal]

Okay, I would vote for it to have more prioritization. I think I can work around it by not including the created filter when I have the customer filter set since other logic downstream will ensure it is within the time frame, but it certainly would be nice if I didn't have to so there was more consistency in the code between testing in staging and running in production.

[strong mantle]

Yeah I added this discord thread to the bug report

Hopefully there's some traction on it soon but I can't guarantee any sort of timeline

[brazen seal]

It would probably still be worth calling out in the docs I linked to for now for others to at least be aware of even if you intend to fix eventually.

[strong mantle]

Yeah I'll suggest it to the team

[brazen seal]

Thanks for your help!