We are running the subscription rollover in test at the moment and for the most part its working, but we're getting a very small number of orders that refuse to generate rollover orders. We believe the common denominator is that the original orders from this past year were altered in some fashion, such as package seats were moved before printing, or exchanged is that order or another order, or the customer account was merged into another account. But only thing is that there were other orders where things like that took place that still rolled over just fine. The actual error message was: "MOS 13 is not assigned or is not valid for date." MOS 13 would be our web subscription MOS. Anyone encountered this issue before?
Hi Jesse,
I've encountered that error before, and it means that the MOS that you're using in your rollover set is not assigned to the performance that you're trying to roll over. I hope this helps!
We actually did discover the issue. It was related to that MOS issue, but it was because we had forgotten to add in a date to the "Add to orders after dt" parameter. So it was trying to add products to orders from a year ago where the MOS was out of range.