TrueContext Status Page

May 8, 2026 · resolved May 8

Salesforce connectivity has been restored. Customers with broken Salesforce Connections are required to reconnect their Connection, after which functionality will return. If you are still experiencing issues after reconnecting, please contact support.

Apr 30, 2026 · resolved Apr 30

This incident has been resolved.

Oct 20, 2025 · resolved Oct 20

This incident has been resolved.

Oct 2, 2025 · resolved Oct 2

**Service Degradation Update - October 1-2, 2025** Given the service degradation over the past two days, we wanted to provide detail on what happened and our path forward. **Incident 1 - October 1** At 11:30am EDT, we detected excessive pressure on our persistence store. We immediately rolled back a change released earlier that morning and performed manual actions to reduce system pressure. Service incrementally recovered to normal operation within one hour. We removed all changes from the prior 24 hours to investigate further, and those changes currently remain removed. **Incident 2 - October 2** At 10:00am EDT, approximately 30 minutes after deploying a new changeset, we noticed degraded response times, though not as severe as the prior day. We immediately initiated a rollback, which did not resolve the issue. A second, more extensive rollback also had no effect. Further analysis indicated the issue was likely triggered by increased activity volume during weekday morning hours rather than our code deployments. Given the reduced severity of this incident, we were able to investigate more thoroughly while maintaining acceptable service levels. We manually restored full system operation by early afternoon. **Current Status and Next Steps** * We have identified potential root causes and are actively investigating * Out of an abundance of caution, all code deployments are paused until we conclusively identify the root cause * We are implementing additional monitoring to detect similar issues earlier * We have created an additional response playbook with mitigation measures to resolve this type of incident more quickly We apologize for the disruption this has caused. We are committed to identifying and safely resolving the underlying root causes to prevent recurrence.

Oct 1, 2025 · resolved Oct 1

This incident has been resolved.