This does indeed seem like unusual behavior. The currentPeriodEnd should be based on the interval specified in your subscription plan. If it’s set to EVERY_30_DAYS, then this date should be 30 days after the createdAt date.
There could be several possible explanations for this issue. Here are a few troubleshooting steps:
Check the subscription settings in your app: Ensure that the interval for the subscription plan is correctly set to EVERY_30_DAYS. Also, ensure that there are no specific settings or conditions in your app that might be influencing the currentPeriodEnd.
Check if the issue persists across multiple subscriptions: Try creating another subscription and see if the same problem occurs. If it’s a one-off issue, it might have been a temporary glitch.
Check for any API errors: Carefully review your API response for any errors or warnings that might indicate what’s going wrong.
Try the above troubleshooting steps and let us know if you’re still running into issues - hope this helps!
Check the subscription settings in your app: As you can see the interval in the API Response is correctly setup to “interval”: “EVERY_30_DAYS” I also checked for any specific setting that could cause this issue but I didn’t find anything.
Check if the issue persists across multiple subscriptions: Yes it does. It passed 5 days now and it still happening on every subscription that I create on many development stores.
Check for any API errors: There is not any error. Here I have the subscription create response and as you can see all looks good:
Sorry, I didn’t find any solution yet. Somewhere else I read that it was an issue that happens when the test field is true, so hopefully this is not happening on production, it’s just a testing behavior. So I just workaround it for the meantime.
Hey @Liam ! Any suggestion about how to proceed with this issue? Who/where should I contact to reach the right person to let them know about this failure?
Hi @CharlyTalavera ,
We fixed an issue with the currentPeriodEnd value on test charges. Can you please try creating new charges and let us us know if you’re still running into problems? Thank you for your patience on this!