A permanent fix has been implemented to prevent this happening again in the event of a node failure.
If you have been affected we will be in contact about the next steps to resolve any affected customers or subscriptions.
After diving deeper, affected customers appear to be 26 in total and affected orders in the region 50.
We will be following up shortly with news on permanent solution and route to resolution for the above - whether manual or programmatic.
Issue has been resolved with temporary fix, but please stand by for fix / recommendation for affected subscriptions/orders. Permanent fix is being implemented.
Upon further investigation this issue was specifically relating to rendering of emails. This means some orders being marked as shipped by old order management system and ShipStation may have failed. Estimated impact below.
Total potentially affected new subscriptions/checkouts: 89
Total potentially affected ShipStation/batch orders marking orders as shipped : 24
Recommended and decided resolution steps and actions for the affected to be confirmed.
In the middle of last night (2am BST) a node had to have its power cycled due to it crashing, this is pretty routine, and nothing to be alarmed about.
However when it re-booted there was a new issue which caused some issues with a percentage of checkouts showing an error when it had actually succeeded. Some customers due to thinking the checkout had failed re-attempted multiple times resulting in multiple subscriptions.
The server has been pulled out of rotation and will be diagnosed and fixed in the coming hours.
We apologise for any inconvenience for your or your customers.