#dylanfm
vestal girder
simple acorn
Hi there!
somber socket
req_bQjMQV89JzMsJb
simple acorn
How can I help?
somber socket
I have done quite a bit of testing previously on scenarios where the subscription schedule starts immediately and also when it starts in the future. This request is an example of it starting in the future.
What has tripped me up is the null subscription
Earlier testing didn't get caught out by this which is why I'm wondering if the behaviour changed or if I have been lucky/unlucky
Isn't clear through API docs whether this field would be null at times. I had assumed it's always present.
simple acorn
If you are making a subscription schedule to create a subscription in the future, then the subscription object will be created in the future. So it's expected that's it's null for now.
somber socket
Ok wow, I'm confused why this has worked for me in the past. To provide context this is an insurance product in development that I started a year or so ago. I've returned to testing payment scenarios today and triggered this. I wonder how it was working before? I'm sure that future payments were working ok.
simple acorn
Hum, can you share a subscription schedule ID where you saw this different behavior?
somber socket
Ok, I'll try to dig up an old one. Although its future then would likely be our past now, so it may have changed!
Actually PEBKAC here. Reviewing git blame I can see a change from March 8 where I introduced the expectation that subscription is never null. Thanks for confirming that it is null until the schedule comes into effect.
simple acorn
Happy to help 🙂