Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Formstack Outage History

Every past Formstack outage tracked by IsDown, with detection times, duration, and resolution details.

There were 143 Formstack outages since July 2017. The 19 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 20, 2026

May 2026: Formstack Documents Returning 404 Errors When Accessing Documents and Builder Tabs

Detected May 20, 2026 9:32 AM EDT · Resolved May 20, 2026 10:30 AM EDT · Duration about 1 hour

Formstack Documents users experienced 404 errors when trying to access the OnlyOffice builder experience, preventing them from using this specific document building functionality. The API & Document Generation components were affected, while native builder features, file management, and PDF uploads continued working normally. The issue was identified and resolved within 58 minutes through a targeted fix.

Major May 12, 2026

May 2026: reCaptcha Verification Login Loop

Detected May 12, 2026 10:53 AM EDT · Resolved May 12, 2026 12:01 PM EDT · Duration about 1 hour

Formstack experienced a major incident where reCAPTCHA verification during login was stuck in a loop, redirecting users back to the verification step instead of completing the login process for a limited number of accounts. The issue prevented affected users from successfully accessing their accounts for 1.1 hours. The problem was resolved and users can now log in normally without being redirected back to the verification step.

Minor May 11, 2026

May 2026: Investigating intermittent Salesforce Delivery authentication and merge failures.

Detected May 11, 2026 12:21 PM EDT · Resolved May 11, 2026 3:18 PM EDT · Duration about 3 hours

Formstack experienced intermittent Salesforce Delivery authentication and merge failures due to recent Salesforce OAuth/security changes, affecting the API & Document Generation components for 3 hours. Users encountered "INVALID_SESSION_ID: Session expired or invalid" and "Could not refresh your Salesforce access token" errors, with temporary workarounds requiring re-authentication of Salesforce connections. The engineering team identified and implemented a fix, resolving the issue while advising customers to re-authenticate their Salesforce connections if delivery problems persist.

Minor May 8, 2026

May 2026: Streamline: Workflow Issue Between Forms and Document Steps with Mapping

Detected May 8, 2026 2:15 PM EDT · Resolved May 8, 2026 3:09 PM EDT · Duration about 1 hour

Formstack experienced a workflow issue in Streamline where sessions encountered unexpected behavior when transitioning from Forms steps to Document steps with field mappings configured between them. The issue affected workflow functionality for users utilizing these specific step transitions with mappings. The problem was identified, a fix was implemented and monitored, and the incident was resolved after 54 minutes.

Minor May 8, 2026

May 2026: Customers intermittently prompted to sign in while signing Formstack Sign documents

Detected May 8, 2026 2:11 PM EDT · Resolved May 8, 2026 2:41 PM EDT · Duration 31 minutes

Formstack Sign experienced an issue where users were intermittently prompted to sign in while attempting to sign documents, affecting the Documents component. The incident lasted 31 minutes and was resolved, with users able to complete the signing process by retrying the action or reopening the signing link if they continued to experience issues.

Minor April 29, 2026

April 2026: Formstack Sign API Not Updating Document Status

Detected Apr 29, 2026 11:05 AM EDT · Resolved Apr 29, 2026 1:41 PM EDT · Duration about 3 hours

The Formstack Sign API experienced an issue where it failed to reflect updated document statuses after signing completion, though the signing workflows themselves continued to function normally. This caused some integrations to not receive correct status updates for completed documents. The issue was identified, fixed, and resolved after 2.6 hours of monitoring.

Major April 24, 2026

April 2026: Streamline Experiencing Errors in Project Workflows

Detected Apr 24, 2026 9:25 AM EDT · Resolved Apr 24, 2026 9:46 AM EDT · Duration 21 minutes

Formstack's Streamline service experienced errors in project workflows, with users encountering "Something went wrong" messages while progressing through affected workflows. The issue was caused by a frontend problem introduced in a recent deployment. The incident was resolved after 21 minutes once the engineering team identified and implemented a fix.

Minor April 14, 2026

April 2026: Streamline Workflow Session Disruption

Detected Apr 14, 2026 8:58 AM EDT · Resolved Apr 14, 2026 9:39 AM EDT · Duration 41 minutes

Formstack's Streamline workflow service experienced a 41-minute disruption where users were unable to run workflow sessions in production due to an issue with the us.streamline.intellistack.app domain. A temporary workaround was provided by replacing intellistack.app with formstack.app in session URLs. The issue was identified and resolved, with users advised to clear their browser's DNS cache if problems persisted.

Minor April 10, 2026

April 2026: Forms: Partial Submissions Unavailable

Detected Apr 10, 2026 12:06 PM EDT · Resolved Apr 10, 2026 12:47 PM EDT · Duration 40 minutes

Formstack Forms experienced an outage where partial submissions functionality was unavailable for 40 minutes, affecting the main application from 9:02 AM to 12:15 PM EST. The engineering team identified the issue and implemented a fix that restored full functionality. The system was monitored following the resolution to ensure stability.

Major April 7, 2026

April 2026: Sign: Blank page when logging in

Detected Apr 7, 2026 9:41 AM EDT · Resolved Apr 7, 2026 10:24 AM EDT · Duration 43 minutes

Formstack Sign experienced a major incident where customers encountered a blank screen after logging in, preventing access to the main application. The issue affected user authentication and application access for 43 minutes. The team identified the root cause, deployed a fix, and confirmed that customers could successfully log in and access the application normally.