Disruption to Automatic Downloads in DonorCentral

Published
An issue has been discovered that impacts the automatic upload of data from FIMS to DonorCentral. Over the weekend, we performed manual data uploads while actively investigating the issue; therefore the most recent available data was uploaded to DonorCentral the night of Sunday, January 15. The nightly upload has been temporarily turned off until the issue is resolved. We apologize for any inconvenience this may cause, and will provide you with a situation update tomorrow.

If you have questions, the MicroEdge Technical Support team is available Monday through Friday, from 8am to 8pm (ET) and can be contacted in one of the following ways:
Phone: 800.256.7772
Online: 
Log into the PowerME portal, click the Cases tab at the top of your PowerME homepage, and then click Create New Case

Leave a Comment

6 Comments
Our thanks to you and the team, Collin.
Our testing is complete and DonorCentral accessibility has been restored. All automatic uploads of data from FIMS to DonorCentral have also been restored, and all data in DonorCentral is up to date. We will send a formal "success" email later tonight.
We are finishing up the last step in the deployment process. The process is taking a little more time than expected and we need up to two additional hours for final testing in production before we turn on DonorCentral. The new target completion time is 5 p.m. ET. I apologize for any inconvenience. We will provide an update when we are complete.
Following up on the email sent, last week, to all designated contacts for DonorCentral. We are currently deploying the fix to the nightly upload issue. While we deploy, DonorCentral will not be accessible from 5 a.m. - 3 p.m. ET today. We apologize for any inconvenience this may cause, and will update you again after the fix has been implemented.
One clarification to the above note: We have temporarily turned off both the nightly upload process and the ability to manually upload data from FIMS to DonorCentral. We are running our fix through another round of testing to confirm earlier results. We will share details of the deployment plan, shortly.
We are testing a fix in our staging environment and preparing an email communication with the plans to deploy the fix to production. We will follow-up with the additional details by the end of this week.

Share: