確認メール
Outage重大なインシデント
影響を受けたコンポーネント
Email System (SendGrid)
- investigating
フォームスタックフォームから送信された確認メールに影響を及ぼす問題を特定しました。 フォームからの確認メールは現在、設定画面から送信されたテストメールを含む、遅延または配信されません。 通知メールは影響を受けません.
- monitoring
修正が実施され、結果の監視
- resolved
事件は解決しました
公式のインシデント更新を自動翻訳しています。
56 Formstack incidents · 2025年5月 — official updates, affected components, duration and resolution details.
フォームスタックフォームから送信された確認メールに影響を及ぼす問題を特定しました。 フォームからの確認メールは現在、設定画面から送信されたテストメールを含む、遅延または配信されません。 通知メールは影響を受けません.
修正が実施され、結果の監視
事件は解決しました
公式のインシデント更新を自動翻訳しています。
現在、一部の顧客は、バウンスされた確認メールに関連する予期しないアカウントの非アクティブ化通知を受信する可能性がある問題を調査しています。 当社のチームは、原因を特定するために積極的に取り組んでいます。 情報が増えるにつれて、追加アップデートが提供されます.
Microsoft-hostedメールアドレスへの確認メール配信に影響を及ぼす問題が解決されました。 確認メールは、期待通り転送されます。 今後もさらなる課題を監視してまいります.
この問題は解決しました。 Microsoft-hostedメールアドレスへの確認メールが届きました.
公式のインシデント更新を自動翻訳しています。
We are currently experiencing an outage affecting Formstack Forms that started at 4:03pm EST. The application is unavailable and returning 504 errors. Form submissions through the web interface are also unavailable. API submissions are still working. Our team is actively investigating the issue and working to restore service. We will provide updates as more information becomes available.
As of 4:26pm EST Formstack Forms is available, and form submissions through the web interface are now processing as expected. Our team is continuing to monitor the service to ensure stability.
This incident has been resolved. Formstack Forms is available and operating as expected. From 4:03 PM to 4:26 PM EST, the Formstack Forms application was unavailable and returned 504 errors. During this time, form submissions through the web interface were also unavailable. API submissions remained operational throughout the incident. Our team monitored the service following recovery and has confirmed that functionality has been restored.
Microsoft is currently experiencing an Exchange Online service issue that may impact customers using Microsoft 365 to send email through Formstack. Customers using Microsoft 365 to send merged documents through Formstack may experience merge errors and failed email deliveries. Customers may also encounter an error when attempting to authenticate or re-authenticate their Microsoft 365 email connection. No other Documents delivery services are impacted. Microsoft is working to restore service. We will provide additional updates as they become available.
Microsoft has completed its investigation and confirmed that Exchange Online remained healthy throughout the event. The issue has been identified as a DNS-related problem affecting Proofpoint, a third-party email service used to route external email traffic. Proofpoint has identified the root cause and is currently working to recover affected services. Formstack Documents customers whose Microsoft 365 email traffic is routed through Proofpoint may experience failed email deliveries or DNS-related errors when sending merged documents to external recipients. We are continuing to monitor the situation and will provide additional updates as they become available. Customers can also follow the latest updates on the Proofpoint Current Incidents status page at https://proofpoint.my.site.com/community/s/proofpoint-current-incidents.
This incident has been resolved. Our team identified and corrected a configuration issue affecting Microsoft 365 email delivery through Formstack Documents. Customers should now be able to send merged documents as expected. We apologize for the disruption and appreciate your patience.
大規模な形態の移行に影響を及ぼす問題を特定しました。 当社のチームは調査中、潜在的な問題や失敗したマイグレーションを避けるために、大きなフォームの移行を控えてください。 根本原因を特定し、情報が増えるにつれて、アップデートを提供できるよう積極的に取り組んでいます。 誠に有難うございます.
当社では、限られた数のお客さまに、非常に大きな形態の形態の移行に影響を及ぼす問題を特定しています。 これらの移行は、予期しない問題に失敗したり、経験したりする可能性があります。 チームワークは決議に取り組んでいますが、非常に大きな形態を移行することを控えてください。 7月20日(月)までに、実質的なアップデートを予定しておりません。 追加情報を共有します。 誠に有難うございます.
この問題の修正には引き続き取り組んでいます。
Resolved (Sandbox): 大規模なフォームのマイグレーションの問題の修正はサンドボックスに展開されています。 サンドボックスに影響を受けたお客様は、影響を受けたフォームを再発行して、期待する機能を復元する必要があります。 現在、修正をプロダクションに展開しています。 生産修正がリリースされたら、別のアップデートを行います.
公式のインシデント更新を自動翻訳しています。
We are currently investigating reports of users receiving errors when accessing Formstack Documents through the OnlyOffice builder experience. At this time, we are seeing impact specifically related to the OnlyOffice builder. Native builder functionality, Manage Files access, and PDF uploads are currently operating as expected. Our team is actively working to identify the root cause and assess the full scope of impact. Additional updates will be provided as more information becomes available.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating reports that some users are unable to save changes to existing forms, publish form updates, or duplicate forms within Formstack Forms for Salesforce. Our team is actively reviewing the issue and gathering information to determine the scope and root cause. Based on our initial investigation, the issue appears to be related to Salesforce Summer '26; however, we are continuing to validate this finding and work toward a resolution. We will provide additional updates as our investigation progresses. Thank you for your patience while we work to resolve this issue.
The issue has been identified and a fix is being implemented.
We have identified and resolved the issue affecting form save, publish, and duplicate functionality within Formstack Forms for Salesforce. A fix has been released in version 4.155, and we are actively deploying this update to affected organizations. If you would prefer to install the update immediately, you can do so using the following package installation link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tg7000000BJDt We will continue monitoring the environment to ensure stability following the deployment. Thank you for your patience while we worked to resolve this issue.
We are currently investigating an issue where the Integration Settings page is not loading for some users. Our team has identified the underlying cause and is actively working on implementing a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of users are unable to create, upload, replace, or save documents. Our team has confirmed the issue and is actively working to identify the root cause. We will provide updates as more information becomes available. At this time, document generation and merge functionality continue to operate normally and are not impacted by this issue.Thank you for your patience while we work to resolve this.
We have identified the cause of the issue affecting document creation, uploads, replacements, and saving. A fix has been developed and is currently being prepared for deployment. We expect the fix to be implemented within the next hour. Document generation and merge functionality continue to operate normally and are not impacted by this issue. We will provide another update once the fix has been deployed or if our timeline changes.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue affecting some in progress workflow sessions that include the Data Search step. Our engineering team is actively working on a fix. New updates will be shared as we learn more.
We have implemented a fix and are continuing to monitor workflow session performance to ensure stability.
We are continuing to monitor for any further issues.
This incident has been resolved. We implemented a fix and affected workflow sessions successfully resumed processing.
We are currently investigating reports of users receiving 404 errors when accessing Formstack Documents through the OnlyOffice builder experience. At this time, we are seeing impact specifically related to the OnlyOffice builder. Native builder functionality, Manage Files access, and PDF uploads are currently operating as expected. Our team is actively working to identify the root cause and assess the full scope of impact. Additional updates will be provided as more information becomes available.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating an issue where reCAPTCHA verification during login is looping back to the verification step for a limited number of accounts. Our team is actively investigating the root cause.
The issue affecting reCAPTCHA verification during login has now been resolved. Users should be able to log in successfully without being redirected back to the verification step. We appreciate your patience while our team investigated and implemented the fix.
Due to recent Salesforce OAuth/security changes, some customers may experience Salesforce Delivery/authentication failures. Affected users may experience merge or delivery failures accompanied by errors such as: “INVALID_SESSION_ID: Session expired or invalid” “Could not refresh your Salesforce access token” In some cases, re-authenticating the Salesforce connection temporarily restores functionality, though reports indicate the issue may recur.Our Engineering team is actively investigating. We will continue to provide updates as we learn more.
The issue has been identified and a fix is being implemented.
We have implemented a fix and are currently monitoring the results.Some customers may still need to re-authenticate their Salesforce connection before Salesforce Delivery resumes successfully. If you continue to experience merge or delivery failures, please re-authenticate your Salesforce connection and retry the affected delivery. We will continue monitoring the situation and provide additional updates as needed.
This issue has been resolved. Some customers may need to re-authenticate their Salesforce connection before Salesforce Delivery resumes successfully. If you continue to experience merge or delivery failures, please re-authenticate your Salesforce connection and retry the affected delivery. We appreciate your patience while our team investigated this issue.
We have identified an issue in Streamline workflows where workflow sessions may experience unexpected behavior when transitioning from a Forms step to a Document step with field mappings between the steps. Our team is currently working on a fix.
We have identified an issue in Streamline workflows where workflow sessions may experience unexpected behavior when transitioning from a Forms step to a Document step with field mappings configured between the steps. A fix has been implemented, and we are currently monitoring the results.
This incident has been resolved.
We are investigating reports of customers being intermittently prompted to sign in while signing Formstack Sign documents.
The issue causing some users to be intermittently prompted to sign in while signing Formstack Sign documents has been resolved. If any users continue to experience the issue, retrying the action or reopening the signing link should allow the signing process to complete successfully. We appreciate your patience while our team investigated and resolved the issue.
We are currently investigating an issue where the Formstack Sign API may not reflect updated document statuses after the signing process is completed. Signing workflows are completing successfully, but some integrations may not receive the correct status updates. Our team is actively working to identify and resolve the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of errors affecting some Streamline projects. Impacted users may see a “Something went wrong” message while progressing through affected workflows. Our engineering teams have identified a likely frontend issue introduced in a recent deployment and are actively working to confirm root cause and prepare remediation. We will provide another update as soon as more information is available.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating an issue affecting workflow sessions in Streamline (us.streamline.intellistack.app), where users may be unable to run sessions in production. Workaround: As a temporary solution, replace intellistack.app with formstack.app in Session URLs.
The issue has been identified and a fix is being implemented.
The issue affecting workflow sessions in Streamline (us.streamline.intellistack.app), where users were unable to run sessions in production, has been resolved. If you continue to experience issues, please clear your browser’s DNS cache: In Chrome: chrome://net-internals/#dns → Clear host cache In other Chromium-based browsers (e.g., Edge): replace chrome:// with the appropriate scheme (e.g., edge://net-internals/#dns)
Partial Submissions in Formstack Forms are currently unavailable. The issue has been identified, and the engineering team is actively working on implementing a fix while systems are being closely monitored.
Partial Submissions in Formstack Forms were temporarily unavailable. A fix has been implemented and functionality has been restored. We are now actively monitoring the system.
We are continuing to monitor for any further issues.
The incident occurred at 9:02 AM EST. A fix was implemented and released, restoring functionality at to 12:15 PM EST, and the issue is now resolved.
We have identified the cause of an issue where customers experience a blank screen after logging in. Our team is actively working on implementing a fix.
A fix has been released for the issue causing a blank screen after login. You can now be able to successfully log in and access the application.
This incident has been resolved. A fix was released and we have confirmed that customers are now able to log in and access the application normally.