Issues with automatic renewal of memberships

The issue affecting membership auto-renewals scheduled for yesterday has now been resolved.

Following recent system-wide improvements, an unintended malfunction occurred in the automated membership renewal job beginning on the 25th and resulted in some renewals not being processed as expected. While the number of impacted renewals was initially very small, the issue also affected some more renewals scheduled yesterday.

We have since identified the root cause, deployed the necessary fixes, and verified that the renewal process is now functioning correctly. All affected memberships have now been updated automatically.

We sincerely apologize for the disruption and appreciate your understanding.

The fix has been deployed and we’re monitoring the results.

An additional fix is currently under review and being prepared for deployment. We expect it to be deployed within the next 40 minutes. Once deployed, we will run the job to restore the affected memberships. We’ll continue to update you until the issue is resolved.

We’ve deployed a fix and are currently re-running the impacted job to restore the affected memberships. While this fix has resolved some of the errors, we are still seeing some remaining issues. Our team is actively working on additional fixes. We’ll continue to share updates as progress is made.

We expect the fix to be deployed within 45-60 minutes. After the fix is deployed, it will require some time for the affected memberships to be automatically restored. We'll continue to keep you updated.

The fix is being reviewed and getting ready to be deployed. We'll updated the status page as soon as it's deployed.

We are continuing to work on a fix for this issue.

We've identified the cause of the issue. Due to this, memberships that were up for renewal last night were not processed correctly. We're currently working on deploying a fix, and once it's in place, we expect all affected memberships to be automatically restored. We'll keep you updated as we progress.

We are currently investigating this issue.