The SpringCM Technology team is working to resolve a performance degradation issue on the NA21 instance. During this time, customers may experience slowness when sending documents for E-Signature and/or workflows failures in associated Send For Signature actions. 

[UPDATE November 5, 2018 at 11:32AM CST]- The SpringCM Technology Team has identified an issue with an errant e-signature automation process, which resulted in a large increase in volume to the E-Signature queue. The issue began on 11/2/2018 10:13PM CT and was addressed via a purging of the E-Signature queue on 11/5/2018 10:42AM CT.

We expect that all E-Signatures processed after 11/5/2018 10:42AM CT will proceed normally.

However, any E-Signature tasks that were affected by the issue between 11/2/2018 10:13PM CT and 11/5/2018 10:42AM CT will be automatically re-queued and processed (ETA Pending).

Additionally, any workflows that failed as a result of this issue will need to be restarted or resumed, depending on the design of the workflow. SpringCM Support will be in contact with affected customers regarding next steps for any failed workflows.

[RESOLVED November 5, 2018 at 1:50 PM CST] - The SpringCM Technology Team has re-queued and processed any outstanding E-Signature tasks and all account administrators who raised support tickets have been contacted regarding next steps for the resumption of failed workflows.