#yodon-test-clocks
spiral bronze
waxen oyster
Can you share more details about your use case?
There's no limit to the number of test clocks but each test clock is limited to three customers and three subscriptions: https://stripe.com/docs/billing/testing/test-clocks#restrictions
cerulean leaf
Can you share more details about your use case?
I'm testing our reporting system that provides data on number of users, money coming in, predicted future revenues, etc. The reason for needing a large number of users is to be able to have enough users to see sensible statistics in the test reports coming out of the simulation.
For everything NOT related to billing, we run a simulation that advances our local server time while simulated users join, subscribe to products, change their subscriptions, cancel, etc. (very similar to what your test clocks are designed to do for your system).
We want to extend our test simulator to include reporting on simulated billing data for these simulated users. From a programming perspective, by far the easiest and "best" way (closest to real world system behavior) is if we can have those 1000 simulated users all advancing through simulated time together (which requires 333 stripe clocks), as opposed to running a simulated user through 2 years, rolling back our system clock, running the next user through 2 years, repeated 1000 times.
(Talking about ficticious users engaging in time travel is not easy - hopefully that description made sense)
waxen oyster
Thanks for the context!
There's no limit to the number of individual test clocks you can create. That said, if any of your teammates use the Dashboard to view all test clocks, they may see some latency when trying to load the list of test clocks.
cerulean leaf
Good point! Fortunately we should only be looking at them via API, but the takeaway I should have is to make sure we clean up clocks after use, even if the simulator crashes or is stopped mid-simulation (which if not careful could leave 1000 test clocks hanging around for a month clogging up the dashboard)
waxen oyster
We do automatically delete clocks 30 days after creation (real days, not simulated days 😅 )