Is Formstack Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

Engineers have observed delays processing some merge requests. They are looking into a solution and will update this page soon. No customer action is required at this time.

This incident has been resolved.

Engineers have observed delays processing some merge requests. They are looking into a solution and will update this page soon. No customer action is required at this time.

The google sheets integration is operating normally

We have identified a single form that is causing the influx of the Google Sheets integration requests, and we have isolated that form so it is not slowing others down. We expect other form integrations to move more quickly going forward.

Engineers have identified the problem and are working on a solution. Submissions are still being sent to Google Sheets, and the process is still very slow. We are seeing some submissions taking as long as 5 minutes each.

Engineers have noticed that the integration queue for Google Sheets submissions integrations is processing very slowly this morning. They are looking into a solution and will update this page soon. No customer action is required at this time.

Removing this notification

We have added a few API services to help manage your Subaccounts in Formstack Forms! https://developers.formstack.com/reference/subaccount There are currently three key services to use: 1. GET _/subaccount_ will return a list of all the subaccounts for a single parent account 2. POST_ /subaccount/:subaccount_id/theme/:theme_id/copy_ will copy a Theme from the parent account into a specific subaccount 3. POST _/subaccount/:subaccount_id/form/:form_id/copy_ will copy a FORM from the parent account into a specific subaccount These API services are available now in the V2API on Formstack Forms.

This incident has been resolved.

We are currently experiencing an interruption in our chart generation module, which is affecting the addition of charts to documents processed by Formstack Documents. This issue is linked to recent updates from one of our third-party vendors. Our team is actively working on a solution, and we appreciate your patience as we resolve the matter.

Engineers have monitored performance for the last hour and waving the green flag.

We are continuing to monitor for any further issues.

The engineers have identified the issue and resolved it. The database and web application traffic has been restored and all functions are back to normal. Most live forms were not affected, so consumers filling out forms and creating submissions were not interrupted. The Admin app was slowed down or non-functional for about 10-12 minutes from about 3:25 pm Eastern to 3:26 pm.

The issue has been identified and appear to be resolved.

502 Bad Gateway is an error for all users logging in to the Forms Admin app.

Resolving this notification

We are introducing a new search endpoint that allows you to search all forms in an account for specific submission values. GET /api/v2/submission <https://developers.formstack.com/reference/submission> The primary purpose of this API service is to support customers with GDPR data retention requests and similar. In the past, if an individual requested to be forgotten, searching each form for the submission data they provided (usually an email) was very time-consuming. This new service will allow searching for that attribute across all submission data in the account and provides a list of forms and submissions containing the value. This service is limited to returning 10,000 submissions that match the search at any one time.

We have confirmed this issue is resolved.

At approximately 3:45 pm (Eastern time) on Tuesday January 28, engineers released a change to the Forms SSO Prefill Mapping mechanism to make the data key case-insensitive for custom field mappings when information is coming from the SSO provider. the intention was to make the prefill mapping easier to match and require less precision from the SSO provider. However, it appears to have interrupted some existing prefill-mapping setups, so we have reverted this change (Effective 4:30 pm, Wednesday January 29) while we research another solution.

The issue has been identified and a possible fix has been deployed. Engineers are re-testing field prefill now to ensure the problem is resolved.

When a form uses SSO in its Form Security Settings, a user can select a prefill mapping mechanism to pre-populate form fields from the SSO (Single Sign On) source. Some customers are experiencing this prefill mapping to be unreliable and some custom fields are getting un-mapped upon save. We are investigating the cause of this and will update when we have more news.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are continuing to monitor for any further issues.

The issue has been resolved, and a rolling update is in progress to restore the functionality of canceling and resuming documents. Most documents have already been fixed, and we expect the remaining ones to be fully restored within the next hour. Thank you for your patience as we worked to resolve this matter.

We are currently experiencing a partial outage with Sign. Users are unable to cancel documents sent for signature or resume documents for signing. Our development team has identified the issue and is actively implementing a solution to restore the service to full functionality.

This API change has been released as of 1:00PM Eastern time on October 22nd.

On Tuesday, October 22 we are releasing an update to the API that adds a new value, internal_label, to a few endpoints related to forms, fields, and submissions. If there is no internal label set on a field, null will be returned for this new value. The following endpoints will now include internal_label: GET /form/:id/field GET /form/:id GET /field/:id GET /form/:id/submission (using parameter data=true) GET /form/:id/partialSubmission (using parameter data=true) GET /submission/:id (using parameter data=true) GET /partialSubmission/:id (using parameter data=true) The following endpoints will now accept internal_label: PUT /field/:id POST /form/:id/field To learn more about the new Internal Labels feature, read more here: https://help.formstack.com/s/article/Internal-Labels For more information on how to use the Forms API, read more here: https://developers.formstack.com/reference/api-overview

The engineering team has released a change to PDF exports to continue the export even if the signature file is missing. This will allow customers to resume their business workflows for those submissions that were broken in the time we were having issues with signatures. Unfortunately, the missing signature files can not be recovered, so customers may need to request those forms be re-submitted for the full information to be available. Now that the exports are fully supported again, feel free to re-run exports and email deliveries.

We have identified the root cause of this issue and have resolved it for future submissions. In addition, engineers are working on a solution to enable exports for submissions with corrupted signature files. We will keep this incident open until that solution is in place. In the meantime, re-running exports (manual exports, scheduled exports, email delivery with PDF) will continue to fail.

The engineering team has identified an issue where submissions with signature fields were failing to capture the signature file. Therefore, those submissions were created, but with a corrupt signature file. That missing signature file then prevents a PDF from being created in the area of an email delivery, a manual PDF export, and a scheduled PDF export. According to our records, the signature problem started intermittently at approximately 11:00am Eastern on Saturday October 19th. The submission issue has been solved at this time as of 10:50am Eastern today (Oct 21). This ensures that all new submissions coming in are working properly and adding a signature file. Exports that failed in the past are not resolved at this time and the engineers are researching options.

We are seeing an increase in errors when customers create submission exports using PDF.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently experiencing a service disruption impacting uploaded documents appearing blank in the user interface. Our Development teams are working to identify the root cause and implement a solution. During this time, your Formstack We will be posting additional status updates as soon as they come in.

Starting on September 7th, Formstack was blocking some Stripe traffic due to an automated security setting. Some customers may have experienced failed transactions with a Stripe integration as a result. In addition, some customers may have been directly contacted by Stripe referencing /admin/form/stripeHook. We have restored the connection and verified that this traffic is valid and we have added it to our Allowed List. We apologize for the interruption and any confusion this may have caused. Stripe service was fully restored today (September 11) at approximately 12:00 noon Eastern time.

This API improvement has been deployed and is available now

We have modified the Live Form API to add two new features: 1. Added form.setValues method - to set the values of multiple fields at the same time. This is structured after the field.setValue method that existed previously. form.setValues will execute only one calculation and validation cycle making it a more efficient way to set the values of multiple fields at once. Documentation: https://live-form-api.formstack.com/interfaces/IFormApi.html#setValues 2. Added a Promise<void> return to the setValue(s) methods to allow you to check when the operation is complete. Documentation: https://live-form-api.formstack.com/interfaces/IFieldApi.html#setValue These features are now available in production and available for use on V4 forms.

This API change was released approximately 10:30AM Eastern time on Monday August 26th and we are not seeing any errors.

On Monday, August 26th, we are releasing a change to the Forms API. In the past, the GET /api/v2/form/{id}/html method always returned V3 HTML, regardless of the form version. Requests using the API to retrieve form data, or specifically form HTML data, will now contain an extra property in its response if this form is V4. The property name is v4html and will contain the HTML data for a V4 form. The property 'html' will still default to return V3 HTML data even if the form is V4 for the time being. This new property was added in two different endpoints, the GET /api/v2/form/{id} and GET /api/v2/form/{id}/html. These changes also can be seen in the respective documentation pages. /form/:id https://developers.formstack.com/reference/form-id-get /form/:id/html https://developers.formstack.com/reference/form-id-html-get

We are no longer seeing any errors associated to this incident. Systems are fully operational.

The engineering team has identified the problem and a fix is in place at this time. We will monitor the situation and ensure all the errors are resolved.

We have been notified of an error with the Forms ==> Docs integration where files are no longer being attached to emails

This incident has been resolved. We are no longer seeing anomalous 404 errors in the FS ID (Authentication and Admin) app.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing elevated levels of 404 errors in FS ID. Our engineers are investigating and we will provide more updates shorlty.

Formstack engineers have monitored the solution for the last few days and no further errors are being reported. All integrations are now fully restored.

Formstack engineers have implemented a fix for this integrations issue. This fix will NOT restore integrations where the credentials are missing. However, re-authenticating the integrations will now be "sticky" and will keep the issue resolved. Therefore, customer intervention is required on affected forms. We apologize for the inconvenience this has caused and we continue to strive toward a more reliable and trustworthy experience within Formstack applications.

The issue surrounding the Box.net integration credentials has been identified and the engineers are currently working on a fix. The expectation is to fix this release today (Friday April 19).

Engineers continue to investigate this issue. There are a few meaningful leads, but no conclusive evidence to determine a cause at this time.

The submit-action integration with Box.net is producing intermittent errors. The User will see an error like, "Unable to refresh access token". Reauthenticating the integration will solve the issue, but this solution may be temporary. If the integration authentication has expired, then submissions will be blocked on that form until reauthenticated. It is possible the integration will need to be reauthenticated multiple times until we resolve this issue.

At approximately 9:35am today, the Forms application was returning a 502 ( Internal Server Error) error in both the Admin app and the Live Form. This error was resolved 10:05am this morning.

The Forms app team has not seen these key errors for over two hours now, so we are declaring this issue fully resolved. The forms are currently fixed, however some visitors who previously saw the issue may still have cached data. The recommendation is to either: 1. Clear the browser cache through its settings page 2. Refresh the form’s cache by holding down the Shift key while refreshing the browser page 3. Use an incognito or private browsing window

A fix has been deployed and internal checks are all passing.

Formstack engineers have identified this as a caching / timing issue around the phone validation library on the live form. They are changing the way this loads to eliminate this issue.

Engineers are continuing to research the source of the problem.

Formstack has discovered an issue on some V4 forms where the phone number field is not completing or validating properly. When this happens, it might require the user to clear the field and re-enter the phone number. It is also possible this error will render the form inoperable. This error is intermittent and appears to happen about half the time

On March 26th we updated the V4 API application to standardize the usage of the getValue and setValue functions to set and report values within fields on the form. This caused immediate issues with custom scripts as it required a new way of handling some of the values. Today, March 28th. We released an update that will allow a customer to use either of the options. The old method is deprecated and therefore not in the current API documentation to ensure customers implementing new solutions only find the new functionality. We will keep the app in this state \(with both options available\) as we change the examples to update for the new requirements. When we do remove the old value options, we will communicate a warning to customers using the old values with a how to change before they are removed. We don’t have a timeframe for this at this time.

The Forms team released a change to the V4 API that adapted the shape of the data returned within the getValue and setValue commands. This likely broke some forms' custom code that was using these commands. Some field types were returning simple values and some were returning a labeled array. Now, with this change, all fields will return an array. Review API documentation in this support article for updated information: https://help.formstack.com/s/article/Formstack-most-recent-form-builder-V4-Api-Overview Example of code change // before var someValue = "123abc"; field.setValue(someValue); field2.setValue(field.getValue().value); // after var someValue = "123abc"; field.setValue({ value: someValue }); field2.setValue(field.getValue());

This incident has been resolved.

We have identified the issue and have implemented a solution. Formstack Sign documents are now processed with no delay. We will continue to monitor this activity.

We are currently experiencing a service disruption impacting field placement. Our Development teams are working to identify the root cause and implement a solution.

Starting at approximately 2:15pm Eastern on Feb 13th, some Notification emails from Forms were blocked due to an enforcement of DMARC standards. We saw enough emails being blocked that we relaxed those security settings at 12:00noon on Wednesday the 14th. During that time, it is possible that some Forms emails were redirected to users' spam folders, and it is possible that emails were blocked by users's systems altogether, depending on your organization's email policies. Currently, Formstack utilizes secure settings for both SPF and DKIM, but uses relaxed settings for DMARC. This will be secured in the future, when we can be confident that customer email systems will not block the emails.

The incident is resolved, and our email service is fully operational.

The problem has been resolved, and email delivery has resumed. Newly composed emails are now dispatched promptly without any delays. All emails that were queued during the email service interruption are being sent out in chronological order, starting with the oldest. We anticipate that all backlog emails will be delivered shortly. We apologize for any inconvenience caused by this outage, and we will continue to monitor the situation closely to ensure that email service remains fully operational.

We're still actively working with the SendGrid team to resolve the issue, and they've assured us that this incident is their top priority. As soon as SendGrid resolves it, any pending emails will be promptly sent out.

We are presently encountering delays in document email deliveries. We are actively collaborating with SendGrid to restore our services to fully operational status. Email deliveries through the listed services remain unaffected and are being sent out as usual: - Document delivery via Formstack Sign - Custom-configured SMTP server - Microsoft Office 365 SMTP server - Google SMTP server

We are presently encountering delays in document email deliveries. We are actively collaborating with SendGrid to restore our services to fully operational status.

We are continuing to investigate this issue.

We are currently experiencing an email service disruption impacting Docs email deliveries (excl. Custom SMTP, Google SMTP and Microsoft Office 365) Our Development teams are working to identify the root cause and implement a solution. During this time, emails send from Docs won't be delivered. Custom SMTP, Google SMTP and Microsoft Office 365 emails are not affected. We will be posting additional status updates as soon as they come in.

Workers servers have been fully restored and all queued jobs have been completed as expected. Data and events were delayed for up to 1 hour, and no data loss occurred.

We have identified the issue and are working toward a solution. Resolution expected within 30 minutes.

As of 17:25 Eastern, Forms workers are delayed and queues are backing up. This affects form analytics, submit-action events like form integrations, submission exports, and emails. The Forms application, and the live form is functioning properly.

The issue with submission integrations has been running for some time now. We are marking this as resolved. Remember to re-run submissions for those that failed.

We are continuing to monitor for any further issues.

A fix has been deployed and new errors have been eliminated. System was restored at 10:25am Eastern time.

Errors began at 09:51 Eastern time. Formstack Engineers have discovered the cause and are repairing now.

Forms submissions with a Submit Action integration are failing intermittently. The submissions are being collected, and the integrations will need to be re-run

All notification emails are sending properly. No email traffic was lost.

Formstack has been informed of an outage with the Sendgrid account responsible for sending Notification emails. These are the emails sent to Formstack users indicating that a submission has come in on their forms. Confirmation emails (to people who filled out the form) appear to be working normally.

Through the night, Google Sheets integrations continued to move slowly, and as of 01:05am Eastern on September 28th, all messages had been processed

The Google Sheets submission integration on Forms is performing very slowly at this time. We are processing active submissions into Google Sheets at regular speed. However, a "re-run" of an integration is being delayed by a number of hours. We expect this to be resolved overnight Sept 27th.

Submissions that came into Forms from approximately 4:00pm to 7:00pm were not visible on the submissions list page, creating the impression that the submission feature was broken. No submissions were lost and we have repaired the visibility of them. All submissions should now be visible.

The Forms application had severeley diminished performance from approximately 5:04am to 5:22am Eastern this morning. We have implemented a solution to this now and it is performing as expected.

We have identified the issue and have implemented a solution. Access to your Formstack account and forms has been fully restored. We will continue to monitor this activity and will share more details regarding this incident.

We are currently experiencing a service disruption impacting Forms. Our Development teams are working to identify the root cause and implement a solution. We will be posting additional status updates as soon as they come in.

We have applied an update to our existing 2FA process to mitigate the errors that caused users to resend SMS 2FA requests. Thank you for your patience.

We have identified an intermittent issue with Twilio delivery of SMS 2 Factor Authentication and are working on a fix.

We are currently experiencing an elevated error rate for SMS delivery. Users should attempt to resend the SMS code if they do not receive it. We are investigating the root cause of the issue.

What? On July 20, 2023, we changed the functions within our AWS Cloudfront service so that we could provide more consistent and precise User Agent data inside Form Submissions. Why? When we implemented the previous setup for CloudFront several years ago, it was to provide better filtering of traffic to the Formstack sites to improve safety and security. One downside of that is that Cloudfront was also stripping out the User Agent data from the traffic. We implemented a workaround to capture that information from the Form Submission user interface, but the API was still limited. Now, there are new tools that allow us to have the same level of security, and pass through certain key data, like the source IP and Browser information. What happened? When we added the new filtering setup, we failed to include the API authentication header as allowable information. Therefore, any API connection was refused for a short period of time. When was it down? The Forms API Authentication service was effectively down from 14:29 to 17:05 Eastern Time on 20 July 2023. How was it resolved? When the error rate increased on the API service tracking, we recognized the problem and edited the settings to allow the API Authentication to pass through. We also added the “encrypted form” header information to pass through via API, an additional forgotten attribute. How will this be prevented in the future? Recognizing that the API is a critical service, we added a suite of automated tests around this API Authentication service to ensure that any anomalies are detected well before release to production.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently experiencing a service disruption impacting Sign API Our Development teams are working to identify the root cause and implement a solution. During this time, your integration with Sign may be affected. We will be posting additional status updates as soon as they come in.

API service is restored to normal functioning as of 17:15 Eastern

The Formstack Forms API V2 is returning errors on authentication at a higher than normal rate

The Forms application was intermittently unavailable for approximately 30 minutes on July 18th from 12:37pm to 1:13pm Eastern time due to an partial outage with our AWS infrastructure provider. We have verified all functions are fully restored now.

Statement from Amazon / AWS: Jul 18 10:26 AM PDT Between 9:37 AM and 10:13 AM PDT, we experienced elevated error rates for request serviced by the CloudFront Origin Shield and Regional Edge Cache in the US-EAST-1 region. The issue has been resolved and service is operating normally.

This incident has been resolved.

We are experiencing a service disruption impacting Office for the web integration that allows for online editing of Office files within the Docs app. Our Development teams are working to identify the root cause and implement a solution.

AWS has reported all services have been fully restored to normal operation.

AWS has reported the root issue has been identified and a resolution has been applied. Services are beginning to recover to normal operations. AWS is continuing to monitor service recovery across all services.

AWS has reported system degradation that is affecting some services utilized within Formstack Sign and Copilot. The issue has been identified and Amazon is working on implementing the resolution expediently. Our engineering teams continue to monitor until the services are fully restored. https://health.aws.amazon.com/health/status

We have verified that there have been no more indications of issues with our messaging service from Twilio. This issue is resolved and full functionality is restored to Formstack customers.

We have a fix in place for this issue that restores the SMS functionality between Formstack and Twilio. Users with two-factor authentication setup using text messages are now able to login. Thank you for your patience!

We have verified that our connection to Twilio for providing SMS messages for two-factor authentication (2FA) is not working to login to Formstack. Our research indicates that SMS messages for Sign are not affected, nor are outbound emails for Formstack. If a customer would like to disable the 2FA requirement on their account while we troubleshoot this, feel free to submit a support ticket and we can help edit your account settings.

We are aware that some users are experiencing difficulty logging in. Specifically, users who have 2 Factor Authentication set up with SMS (text) messages. This is due to an issue with our connection to Twilio, the service provider for the SMS 2FA method.

Normal system performance has been restored and we are seeing all web traffic and API services back to normal. Outage was from approximately 11:40am to 11:53am US Eastern time

This issue has been resolved and we are monitoring the stability of the system:

The Forms application is currently down due to an unplanned spike in system load. We expect to restore service soon.

This incident has been resolved.

All of our systems are now operational.

A fix has been implemented and we are monitoring the results.

We are currently experiencing an intermittent outage with Formstack For Salesforce Forms Application. Our team is working to resolve the issue as soon as possible. Below are the details of the Outage. Description/Impact: All parts of the Formstack For Salesforce Forms application for some customers could have been impacted, publish Form. At this time, all of the Forms should be fully functional. Next Steps: No steps need to be taken at this time for our customers. Our internal teams will continue to monitor the issue. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

At approximately 8:30am EST, we have identified a spike in job delays in the Forms Google Sheet Integration. An update was performed on some of the libraries this morning which may have impacted the performance. The updates have since been reverted, and the delays have ceased at this time. We will continue to monitor for any repeat events.

We have been monitoring both the database and the application and have seen consistent performance over the past two days. We are now considering this issue resolved.

We are currently experiencing an intermittent outage with Formstack Forms Application. Our team is working to resolve the issue as soon as possible. Below are the details of the Outage. Description/Impact: All parts of the Formstack Forms application for some customers could have been impacted including submissions, integrations, and access to Formstack Forms. At this time, all of Forms should be fully functional. Next Steps: No steps need to be taken at this time for our customers. Our internal teams will continue to monitor the issue. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

We are currently experiencing an intermittent outage with Formstack Forms Application. Our team is working to resolve the issue as soon as possible. Below are the details of the Outage. Description/Impact: All parts of the Formstack Forms application for some customers could have been impacted including submissions, integrations, and access to Formstack Forms. At this time, all of Forms should be fully functional. Next Steps: No steps need to be taken at this time for our customers. Our internal teams will continue to monitor the issue. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are currently experiencing an intermittent outage with Formstack Forms Application. Our team is working to resolve the issue as soon as possible. Below are the details of the Outage. Description/Impact: All parts of the Formstack Forms application for some customers could have been impacted including submissions, integrations, and access to Formstack Forms. At this time, all of Forms should be fully functional. Next Steps: No steps need to be taken at this time for our customers. Our internal teams will continue to monitor the issue. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

Zuora’s degradation of service has been resolved; current billing functionality has been restored. Please try to execute the previous billing service again. Thank you.

Zuora (Formstack’s billing provider) is having a degradation of service, as a result, your account’s administrative billing function is currently nonfunctional. Our teams are monitoring the billing provider’s site for updates and resolution. Description/Impact: You will receive a 500 error page when you try to do any of the following: change your plan, update a credit card, and view invoices. Next Steps: We will continue to monitor the billing provider’s status. Once it has been restored, please retry the billing process again. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

The Formstack Forms plugin issue has been resolved. Thank you for your patience as we worked through this issue toward resolution.

We have identified an issue with the Formstack Form plugins path; services below will be impacted. - Field Autofill - Confirmation Page - Discount Codes - Share Buttons - Campaign Tracking - Partial Submissions Next Steps: Please follow the status page for next steps once a fix is deployed. We apologize for any inconvenience this has caused and thank you for your patience. We will provide further updates as soon as they are available.

The issue has been fully resolved since 6:30 AM EST. If you're still experiencing issues please contact our support.

We identified an issue within Formstack Sign which prevented documents from being created and sent to participants, as well as, allowing participants to sign documents that were generated and sent to them. A fix has been identified and implemented and we are monitoring results. Users who attempted to send or sign a document in the last 10 hours will need to resend or resign documents in order to complete the process. For documents that are stalled in field placement, users will need to resume them manually.

On Thursday, 02/16/2023, at approximately 1:05 pm EST, during routine maintenance, it was discovered that Forms email deliveries ceased operations. The root cause was identified and addressed, and operations were fully restored at 3:10pm EST. While any submissions which took place during this period were not affected, any emails that failed to send during the down period are not recoverable.

The Google Spreadsheets integration in Formstack Forms has been restored to full functionality. Users should now see a near real-time submission to their spreadsheets as normal.

Google Spreadsheets integration has been restored and forms are submitting data as normal. There will still be a delay as the system is processing the queue of data. Will update when integration times are back to normal.

The Google Sheets integration with Forms continues to perform slowly. Many submissions were processed overnight, but the queue is still quite large and moving slowly. Engineers will research the problem today and update with a fix. Please do not re-run integrations as that will only build the queue.

Forms with a Google Sheets integration will see a delayed delivery of submission data to their Google Sheet on January 23. We expect this delay to be resolved overnight and regular function to be restored by 08:00 Eastern on January 24.

We have completed Help Center maintenance (help.formstack.com) as of 7:30 PM ET today. Thank you for your patience. We are continuing additional QA testing and through Friday 1/20 but this will not impact Help Center performance. You can view the Release Notes article to see a list of changes to the Help Center. If you have any feedback or questions about the updated design, please reach out via our Help Center Feedback Form. Release Notes: https://help.formstack.com/s/article/Formstack-Help-Center-Release-Notes Help Center Feedback Form: https://formstack_ops.formstack.com/forms/formstack_help_center_feedback

The Help Center is undergoing routine maintenance on Thursday, January 19th, beginning at 12:30 PM ET. This only impacts the Help Center homepage and support articles on http://help.formstack.com and will not impact our applications. During this period, there may be performance issues with page loading and changes to navigation occurring in real-time. URLs to direct articles will not be affected. Upon completion of the maintenance window, we will send a follow-up announcement with more details.