I have noticed an oddity during testing of some subscription Selling Plans, namely the Billing Cycles generated for a new subscription seem incorrect when defining an array of anchors in the recurring billing/delivery policies?
Here’s a detailed breakdown on the steps I took to replicate:
I created a test sellingPlanGroup, with a single selling plan, via the sellingPlanGroupCreate mutation.
The main variables in the mutation were an array of billing & delivery anchors that had arbitrary YEARDAY dates applied (Jan 22, May 13, October 2)
This successfully created a selling plan group with a single selling plan.
Querying this group via the
sellingPlanGroup query gave me the following response:
(interestingly, not supplying an interval or intervalCount during creation, defaults to 1-month intervals, but I digress)
Upon subscribing to this selling plan on November 9th, 2025 via my test store, I then queried the Billing Cycles for my new Subscription Contract via the subscriptionBillingCycles query, I got my JSON response with a sequence of billing cycles - which look correct in terms of aligning with the parent selling plan’s anchor dates… except for cycle number 2, which has a cycleEndDate one second before the cycleStartDate!
I was wondering if the 1-month interval default was causing the error, so I re-ran the whole test above with a 3-month interval but I still had the exact same billing cycle times come back, with the same issue in cycle 2.