5/28/2018 10:20 AM CDT: The SpringCM Technology team has been made aware of an issue impacting customers using Conga’s SpringCM integration.  This integration is only available for customers hosted on the NA11 instance, and is only impacting a very small number of customers. Impacted accounts are currently unable to automatically store Conga generated documents into their SpringCM repositories via Salesforce.

As of Friday, May 25, 2018 at 6:00 PM, we have escalated the issue to Conga and advised them of updates they will need to make to their integration endpoints to resolve this issue.  If you are using Conga’s SpringCM integration, we ask that your administrator open up a support ticket with Conga so they can be made aware of the impact. You can open a ticket on Conga’s support page here.

5/29/2018 5:00 PM CDT: The SpringCM Technology team has reported as of 2:00 PM today,  that is issue has been resolved.  We have moved the status of the post to RESOLVED after verifying that customers using the Conga integration are no longer being impacted.