The creation of subscription requests depends on the return of a query made to the subscriptions' database, this query is made periodically to identify which subscriptions should be executed in that period, if this query fails or does not return a particular subscription, its cycle is not executed, and no error is logged, thus resulting in a subscription with the nextPurchaseDate in the past.

We have no way of simulating this scenario due to the dependence on other systems.

To adjust the nextPurchaseDate, the end user can pause the subscription and reactivate it. This action will cause the subscription system to recalculate the execution date and the nextPurchaseDate will be updated correctly.

Or the customer can update the nextPurchaseDate of the user's subscription to a future date via the API.