Historial de interrupciones de Formassembly

1. August 28, 2026 at 5:00 PM UTCinvestigating

   Actualmente estamos investigando informes de retraso en el procesamiento que afectan al conector de Salesforce a nivel de formulario y forma notificaciones después de la presentación del formulario para algunas cuentas. Nos disculpamos por cualquier inconveniente que esto pueda causar. Proporcionaremos actualizaciones a medida que se disponga de más información.

2. August 28, 2026 at 5:31 PM UTCresolved

   Se ha resuelto el tratamiento retardado que afecta las notificaciones de correo electrónico y los conectores Salesforce. Las comunicaciones afectadas se procesaron con éxito después de un retraso. Hemos confirmado que ambas notificaciones y conectores están procesando normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 24, 2026 at 8:01 PM UTCinvestigating

   Actualmente estamos investigando informes de lentitud y posibles errores de gateway. Publicaremos más información cuando esté disponible.

2. August 24, 2026 at 9:23 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. August 24, 2026 at 10:55 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 3:19 PM UTCidentified

   El equipo ha identificado una cuestión en la que la presentación de formularios con un campo de carga de archivos hace que la presentación falle. El equipo está aislando una solución para la cuestión.

2. August 20, 2026 at 9:24 PM UTCresolved

   Resolved — Esta cuestión se resuelve. Entre el 18 de agosto a las 1:03 PM ET y el 20 de agosto a las 11:49 AM ET, los archivos adjuntos a las presentaciones de formularios de Government Cloud no se guardaron debido a un problema de configuración de almacenamiento introducido durante un cambio de arquitectura de alojamiento. Las presentaciones de formularios se completaron y se guardaron respuestas; sólo los archivos cargados fueron afectados. Los archivos subidos durante esta ventana no fueron almacenados y no se pueden recuperar. Tendrán que ser presentados de nuevo. Todos los demás datos de respuesta están intactos. Las cargas han estado funcionando normalmente desde el 20 de agosto a las 11:49 AM ET, y hemos verificado cargas exitosas en varias cuentas. Los clientes con preguntas sobre respuestas específicas deben ponerse en contacto con FormAssembly Support.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 5:12 PM UTCinvestigating

   Estamos investigando informes de que las configuraciones de conectores de Prefill y Submit no están cargando. Los formularios que utilizan el conector Prefill SFMC pueden ser inaccesibles actualmente. Nuestro equipo está investigando activamente la causa, y compartiremos una actualización en breve.

2. August 19, 2026 at 5:26 PM UTCmonitoring

   Hemos identificado la causa del problema que afecta a los conectores de Prefill y Submit de Salesforce Marketing Cloud (SFMC) y hemos aplicado una solución. Las configuraciones de conectores deben estar cargando normalmente, y los formularios afectados deben ser accesibles de nuevo. Estamos monitoreando de cerca para confirmar la recuperación completa.

3. August 19, 2026 at 5:41 PM UTCresolved

   Este incidente ha sido resuelto. Identificamos y corrigimos el problema subyacente, y los conectores de Prefill y Submit de Salesforce Marketing Cloud (SFMC) ahora están cargando y operando como se espera. Las formas afectadas son accesibles de nuevo. Tenga en cuenta que un subconjunto de respuestas presentadas entre las 9:20 AM y las 1:20 PM ET el 19 de agosto de 2026 no puede haber sido enviado a Salesforce Marketing Cloud y puede ser necesario ser reprocesado manualmente. Recomendamos revisar las respuestas presentadas durante esta ventana y reprocesar cualquier que no sincronizara como se esperaba. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 18, 2026 at 4:03 PM UTCinvestigating

   Estamos investigando informes de que el conector de Salesforce a nivel de formulario y notificaciones de formularios no se procesan cuando se presentan formularios para un subconjunto de cuentas. Estamos investigando activamente y proporcionaremos actualizaciones a medida que se disponga de más información.

2. August 18, 2026 at 5:35 PM UTCinvestigating

   Seguimos investigando el problema.

3. August 18, 2026 at 6:49 PM UTCmonitoring

   Hemos mitigado las demoras de procesamiento que afectan las comunicaciones de conectores Salesforce y forma notificaciones. El procesamiento ha regresado a la normalidad, y las comunicaciones y notificaciones afectadas deben estar pasando ahora según lo previsto. Aclaración: Esto fue un retraso de procesamiento, no un fracaso. Se solicitaron comunicaciones y notificaciones afectadas y deberían completarse automáticamente sin necesidad de ser reprocesadas. Posibles registros duplicados: Si usted reprocesó manualmente una presentación mientras se retrasaba, usted puede ver un registro duplicado en Salesforce — uno de la presentación original y uno del intento de reprocesamiento. Recomendamos revisar las presentaciones recientemente reprocesadas para duplicados.

4. August 19, 2026 at 7:42 PM UTCidentified

   Si bien esperamos que la respuesta de ayer sea una solución completa, los clientes siguen experimentando problemas intermitentes con los retrasos. El equipo ha identificado la causa potencial y está trabajando activamente en esa solución. Seguiremos publicando aquí cuando se disponga de nueva información.

5. August 20, 2026 at 2:51 PM UTCresolved

   Este incidente ha sido resuelto. Por favor, contacte para apoyarte si sigues teniendo problemas.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 13, 2026 at 8:54 PM UTCinvestigating

   We are currently investigating reports that the form-level Salesforce connector and form notifications are experiencing delayed processing upon form submission for some accounts. Our team is actively investigating the issue and will share additional updates as our investigation progresses. Update: Further investigation shows this is a delay in processing rather than a failure to process.

2. August 13, 2026 at 10:09 PM UTCmonitoring

   We identified a period of increased submission volume that resulted in delayed connector and email notification processing. The increased activity has subsided, and processing queues have now caught up. We have not identified any broader service issues and will continue to monitor the situation.

3. August 14, 2026 at 2:08 AM UTCresolved

   Delayed Salesforce Connector and Email Notification Processing on Form Submission has been resolved. Both the Salesforce Connector and email notifications are now running as expected. We apologize for any inconvenience caused and appreciate your patience. If you continue to experience issues, please contact support.

1. August 7, 2026 at 7:27 PM UTCresolved

   Between approximately 2:45pm - 3pm ET a small segment of our Compliance Cloud accounts may have experienced temporary access loss to their forms and/or accounts. This was quickly identified and resolved by our team. There may also be a slight delay in purge jobs associated with this outage.

1. July 24, 2026 at 10:05 PM UTCinvestigating

   Actualmente estamos investigando informes de autorizaciones rotas o inválidas de Salesforce que afectan algunas cuentas. Siga los pasos a continuación para restaurar la conexión: - Antes de reautorizar, compruebe cuántas conexiones activas tiene actualmente en Salesforce. Haga clic en su icono de perfil en la esquina superior derecha de Salesforce, y luego vaya a Ajustes √≥ Gestiones. - En la tabla de aplicaciones OAuth, compruebe cuántas veces aparece FormAssembly Connector. Salesforce permite un máximo de cinco conexiones por aplicación conectada. - Si ya tiene cinco conexiones FormAssembly Connector, revoca cualquier conexión con el recuento de uso más bajo. Esto liberará un token y ayudará a evitar que Salesforce revoque una conexión que todavía se está utilizando activamente. Luego, vuelve a FormAssembly. Revise su nombre de usuario en la esquina superior derecha y seleccione Autorizaciones externas. Reautorizar cualquier conexión marcada como inválida. - Si tiene menos de cinco conexiones, arrastre su nombre de usuario en la esquina superior derecha de FormAssembly y seleccione Autorizaciones externas. Luego, reautorizar cualquier conexión marcada como inválida. Si sigues corriendo en problemas, ponte en contacto con nuestro equipo de apoyo.

2. July 30, 2026 at 10:41 PM UTCmonitoring

   Hemos implementado cambios que abordan varias causas de la autorización de conectores Salesforce, y el número de nuevos informes ha disminuido significativamente. Continuamos monitoreando la situación de cerca y proporcionaremos otra actualización mientras confirmamos la estabilidad de estos cambios.

3. July 31, 2026 at 9:38 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 26, 2026 at 2:47 PM UTCinvestigating

   We have reopened our investigation into reports of connectivity issues from UK customers using BT and EE networks. Although BT previously confirmed that the underlying network issue had been resolved, we continue to receive reports from some customers who are still unable to access FormAssembly. We are working with BT to determine the cause of the continued reports. In the meantime, customers may be able to restore access by connecting through an alternative network, such as mobile data or a different ISP. For reference, our previous incident update is available here: https://status.formassembly.com/incidents/1cgbt78n7h3b We will continue to provide updates as we learn more.

2. August 5, 2026 at 4:32 PM UTCresolved

   The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

1. June 16, 2026 at 7:20 PM UTCinvestigating

   We are aware of an issue affecting customers in the UK accessing FormAssembly via BT Internet Service Provider and its subsidiaries (including EE). Affected users may be unable to reach FormAssembly instances and forms. This issue appears to be network-specific. If you are affected, connecting via an alternative network (such as a mobile data connection or a different ISP) should restore access. Our team is actively investigating. We will provide updates as we learn more.

2. June 24, 2026 at 9:47 PM UTCresolved

   The connectivity issue affecting UK BT and EE customers has been resolved. Access to FormAssembly is now fully restored on these networks.

1. May 21, 2026 at 7:07 PM UTCresolved

   Earlier today, one of our sending IPs was listed on a third-party blocklist, causing some outbound email notifications to be blocked or delayed by recipient mail servers. The IP has since been delisted, and email delivery has returned to normal. We apologize for the disruption.

1. May 20, 2026 at 3:41 PM UTCinvestigating

   Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.

2. May 20, 2026 at 3:43 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 20, 2026 at 4:36 PM UTCresolved

   This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.

4. May 20, 2026 at 6:29 PM UTCpostmortem

   **Update:** We previously marked this incident as resolved, but we have since identified additional accounts that may be affected. Our team is actively investigating and working to restore access. We apologize for the confusion and will continue to provide updates here as we learn more. As a reminder, responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.

1. June 10, 2026 at 5:52 PM UTCresolved

   Between April 22 and May 18, 2026, an issue caused Form Analytics metrics to be recorded incorrectly, resulting in metrics detail loss for that period. Form submissions and response data were not affected. The issue has since been identified and resolved. Our team is actively working to recover form submission counts for the affected timeframe. Please note that other metrics, including form views, drop-offs, and bounced views, will not display data for the affected period. We sincerely apologize for the disruption.

1. April 17, 2026 at 2:09 PM UTCresolved

   Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.” The issue has been resolved, and services have returned to normal. We will continue to monitor.

1. April 7, 2026 at 7:35 PM UTCinvestigating

   Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now. We will post more information as it becomes available.

2. April 7, 2026 at 11:56 PM UTCmonitoring

   We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers. The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally. We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resolved.

3. April 8, 2026 at 2:49 PM UTCresolved

   The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally. If you continue to experience issues, please contact support.

1. March 26, 2026 at 2:50 PM UTCinvestigating

   We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.

2. March 26, 2026 at 3:18 PM UTCmonitoring

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

3. March 26, 2026 at 3:57 PM UTCresolved

   This incident has been resolved.

1. February 12, 2026 at 7:10 PM UTCinvestigating

   We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform. At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked. Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible. We will provide updates here as soon as more information becomes available.

2. February 12, 2026 at 7:55 PM UTCmonitoring

   A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.

3. February 12, 2026 at 8:22 PM UTCresolved

   This incident has been resolved.

1. February 2, 2026 at 8:27 PM UTCinvestigating

   We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission. Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL. Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors. Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.

2. February 2, 2026 at 8:58 PM UTCidentified

   We have identified the cause of the issue impacting form submission redirects. Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made.

3. February 4, 2026 at 8:27 PM UTCresolved

   The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.

1. January 29, 2026 at 2:51 PM UTCresolved

   We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.

1. January 22, 2026 at 11:57 PM UTCidentified

   We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.

2. January 23, 2026 at 7:11 PM UTCresolved

   This incident has been resolved. Please reach out to [email protected] if you run into any further issues.