yathartha_api

[frigid breach]

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

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

[upbeat acorn]

start_date of the billing cycle to november 5
I don't see that, I see that the current_period_start is 2025-01-24 10:38:00 which is the time on the clock

[quick fossil]

Can you please look into lines.data[0].period

there is start and end

and start has 5th of nov

but it is inside latest_invoice key

[upbeat acorn]

Yes I suspect this is just a bug where that timestamp reflects the 'real world' time of the request as opposed to the clock

[quick fossil]

I also have suspected the same, since test clock didnot attached to that date. I hope it would work properly in live env

[upbeat acorn]

Yes live mode invoices will be fine as the test clock is irrelevant there

[quick fossil]

thanks. one request though, can it be fixed so that later we can test few case scenario 🙂

on staging