#claudiuyoro_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/1222519007807148053
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- claudiuyoro_api, 6 days ago, 5 messages
- claudiuyoro_api, 6 days ago, 9 messages
The options are either:
- Use the CLI where you can trigger specific events and even override fields
- Make the API calls yourself to fire the related events, perhaps leveraging a test clock
Hi! Thanks for answering!
As for CLI: can I trigger specifying a subscription Id?
I don't think so as using --override will pass that parameter to the associated API requests (and id is invalid)
By all means try it, but I think it'll error
Hmm, I see.
I tried already test clocks, but I'd like to test also the functionality for fail subscriptions (e.g the user has insufficient money on his card). What would be for this scenario the best practice to test?
Like this:
- User subscribes successfully to a plan
- The upcoming month gets a fail
- Then stripe will retry a few more times
- After that it will cancel the subscription for the user.
I want to handle all these scenarios, does it make sense?
You'd update the default PM on the subscription to be a test card that fails
Then advance the test clock, and the recurring attempts should fail and the dunning settings will kick in (to cancel etc)
I see, it makes sense, thank you!