#raghul-s_api
blazing axleBOT
đ 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/1367863570213240853
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wraith jackal
Hmm I see that too.
It doesn't appear the customer is using a test clock, as far as i can see
blazing axleBOT
winged furnace
No simulation is tried with test clock. Then the subscription should have started by now, right?
reef shore
Hello
Are you saying you did use test clock for this?
To be clear, the subscription should've started already regardless of you using test clock or not. We're looking into this.
winged furnace
I was saying we haven't used the test clock.
Got it. Let me know
reef shore
@winged furnace do you have any other examples of such issues with other schedules? Or just this one?
winged furnace
Yeah, one more. Just a moment
This schedule was also scheduled to start today, but it hasn't
reef shore
Thanks
reef shore
Ah looks like the connected account is in rejected state
which would explain why you're not seeing Subscription Schedules generating a subscription
You can use a different connected account for testing
winged furnace
Oh okay. Got it.
Even the normal subscriptions won't work in this account?
reef shore
Yeah we pause the service that executes logic behind invoices and subscriptions if the associated account is in rejected state
winged furnace
Fine. I'll try with different account. Thanks for the help
reef shore
Sorry for the delay here.. Should've noticed this earlier than we did.