#ian-goldberg_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1237451978158899260
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Are all your test clocks getting this error? Or just a subset?
all of them are from what Ive tested
another developer and I have tested it 5-10 times with the same issue each time
Hello! I'm taking over and catching up...
This can sometimes happen. I had a look broadly and it doesn't appear to be a widespread issue. Can you attempt the operation again after a few minutes?
we tried yesterday afternoon, and it persisted to today
Have you tried a new Test Clock?
hm in the dashboard it doesnt work though, just to "advance time"
Right, I mean abandon that Test Clock entirely and try creating a new one.
ill try
well we arent creating it from test-clocks, we were just creating it from the subscription itself
That should create a new Test Clock for that Subscription. You're saying every time you press that button you're seeing a failure?
yeah exactly, it happened like 10 times, including the request i put in this thread
evt_1PDrSRFNVbYFceRM8fjn1ufA
it just spins its wheels
Does another Subscription work?
We're investigating on our end, but it might take a while to find and fix the issue.
@solemn plaza just catching up and taking over for my teammate.