We identified an issue affecting documents sent to Formstack Sign via the API (including documents triggered by integrations). Direct sends from within Formstack Sign were not impacted. Some customers may have seen “Oops” errors, which were related to the same API issue and a cross-origin policy condition. Resolution: The incident has been resolved, and API sending is functioning normally. Customer action Any documents that failed to send during the incident may need to be resent from the original source system. For example: • If the send was triggered from Formstack Forms, resend by re-triggering the integration on the submission. • If the send was triggered from another integration/source, resend from that originating workflow. The issue was introduced by two releases: • First release — deployed approximately 7 hours ago (Impacts Sign UI-related API behavior and contributed to “Oops” errors) • Secondrelease — deployed approximately 2 hours ago (Impacts delivery from external documents and integration-triggered sends) We apologize for the disruption and appreciate your patience.
Documents → Sign Delivery Resend Guidance: If Debug Mode or “Save Data to Re-Merge / Download Later” was not enabled at the time the document was generated, the document cannot be regenerated in Formstack Documents. In this case, You will need to resubmit from the original data source so it triggers a new delivery to Formstack Sign.
This may involve: • Reprocessing a Formstack Forms submission • Rerunning an automation or integration (for example, Salesforce) • Re-triggering the workflow that originally generated the document This ensures a new document is generated and delivered successfully to Formstack Sign.
Posted Jan 20, 2026 - 13:57 EST
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Jan 20, 2026 - 13:18 EST
Identified
We have identified an issue affecting deliveries to Formstack Sign. Our engineers are actively working to mitigate the issue. We will provide updates as they become available.
Posted Jan 20, 2026 - 12:34 EST
This incident affected: Formstack Sign (Documents).