Formassembly driftsforstyrrelser

1. 28. august 2026 kl. 17.00 UTCinvestigating

   Vi er i øjeblikket ved at undersøge rapporter om forsinket behandling påvirker form- niveau Salesforce stik og danne meddelelser efter formular indsendelse for nogle konti. Vi undskylder for eventuelle ulemper. Vi vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 28. august 2026 kl. 17.31 UTCresolved

   Den forsinkede behandling påvirker e-mail-meddelelser og Salesforce-konnektorer er blevet løst. Påvirkede indlæg blev behandlet med succes efter en forsinkelse. Vi har bekræftet, at både meddelelser og konnektorer nu behandles normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. august 2026 kl. 20.01 UTCinvestigating

   Vi undersøger i øjeblikket rapporter om langsommelighed og mulige gateway-fejl. Vi vil sende flere oplysninger, efterhånden som det bliver tilgængeligt.

2. 24. august 2026 kl. 21.23 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 24. august 2026 kl. 22.55 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. august 2026 kl. 15.19 UTCidentified

   Holdet har identificeret et problem, hvor indsendelse af formularer med en fil upload felt får indsendelse til at mislykkes. Holdet isolerer i øjeblikket et fix for problemet.

2. 20. august 2026 kl. 21.24 UTCresolved

   Opløst - Dette spørgsmål er løst. Mellem 18 august kl. 01: 03 ET og 20 august kl. 11: 49 ET, filer knyttet til Regering Cloud form indlæg blev ikke gemt på grund af en lagerkonfiguration problem indført under en hosting arkitektur ændring. Form indlæg afsluttet og svar blev gemt; kun de uploadede filer blev påvirket. Filer uploadet under dette vindue blev ikke gemt og kan ikke inddrives. De skal indsendes igen. Alle andre responsdata er intakte. Uploads har fungeret normalt siden 20. august kl 11: 49 AM ET, og vi har verificeret succesfulde uploads på tværs af flere konti. Kunder med spørgsmål om specifikke svar bør kontakte FormAssembly Support.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. august 2026 kl. 17.12 UTCinvestigating

   Vi undersøger rapporter om, at Salesforce Marketing Cloud (SFMC) Premill og Indsend stik konfigurationer ikke indlæses. Former, der bruger SFMC Prerill stik kan i øjeblikket være utilgængelige. Vores team undersøger sagen, og vi deler snart en opdatering.

2. 19. august 2026 kl. 17.26 UTCmonitoring

   Vi har identificeret årsagen til problemet påvirker Salesforce Marketing Cloud (SFMC) Premill og Indsend stik og har anvendt en rettelse. Forbindelseskonfigurationer bør nu læsses normalt, og berørte formularer bør være tilgængelige igen. Vi overvåger nøje for at bekræfte fuld bedring.

3. 19. august 2026 kl. 17.41 UTCresolved

   Denne hændelse er blevet løst. Vi identificerede og korrigerede det underliggende problem, og Salesforce Marketing Cloud (SFMC) Premill og Indsend stik er nu loading og drift som forventet. Påvirkede formularer er tilgængelige igen. Bemærk venligst, at en delmængde af svar indsendt mellem 9: 20 AM og 1: 20 PM ET den 19. august 2026 kan ikke være blevet sendt til Salesforce Marketing Cloud og kan være nødvendigt at blive manuelt genbehandlet. Vi anbefaler at gennemgå svar indsendt under dette vindue og oparbejdning enhver, der ikke synkronisere som forventet. Tak for din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. august 2026 kl. 16.03 UTCinvestigating

   Vi er ved at undersøge rapporter om, at form- niveau Salesforce stik og formular meddelelser ikke er behandling efter formular indsendelse til en delmængde af konti. Vi er aktivt at undersøge og vil levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 18. august 2026 kl. 17.35 UTCinvestigating

   Vi fortsætter med at undersøge problemet.

3. 18. august 2026 kl. 18.49 UTCmonitoring

   Vi har afbødet de forsinkelser, der påvirker Salesforce-konnektormeddelelser og meddelelser. Forarbejdningen er vendt tilbage til normal, og berørte indlæg og anmeldelser bør nu gå igennem som forventet. Præcision: Det var en behandlingsforsinkelse, ikke en fiasko. Berørte indsendelser og anmeldelser var i kø og skulle fuldende automatisk uden at skulle ombehandles. Mulige duplikater: Hvis du manuelt genbehandlet en indsendelse, mens det blev forsinket, kan du se en duplikering rekord i Salesforce - en fra den oprindelige indsendelse og en fra oparbejdning forsøg. Vi anbefaler at gennemgå nyligt genbehandlede indlæg for duplikater.

4. 19. august 2026 kl. 19.42 UTCidentified

   Mens vi håbede de sidste dage svar ville være en komplet fix, kunder fortsætter med at opleve intermitterende problemer med forsinkelser. Holdet har identificeret den potentielle årsag og arbejder aktivt på denne rettelse. Vi vil fortsætte med at skrive her, når nye oplysninger er tilgængelige.

5. 20. august 2026 kl. 14.51 UTCresolved

   Denne hændelse er blevet løst. Ræk venligst ud til støtte, hvis du fortsætter med at løbe ind i nogen problemer.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. august 2026 kl. 20.54 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. 13. august 2026 kl. 22.09 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. 14. august 2026 kl. 02.08 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. 7. august 2026 kl. 19.27 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. 24. juli 2026 kl. 22.05 UTCinvestigating

   Vi er i øjeblikket ved at undersøge rapporter om brudt eller ugyldige Salesforce tilladelser påvirker nogle konti. Følg nedenstående trin for at genoprette forbindelsen: - Før du giver tilladelse, tjek hvor mange aktive forbindelser du har i Salesforce. Klik på profilikonet i øverste højre hjørne af Salesforce, og gå derefter til Indstillinger > Administrer forbindelser. - I OAuth Apps bordet, kontrollere hvor mange gange FormAssembly Connector vises. Salesforce tillader højst fem forbindelser pr. tilsluttet app. - Hvis du allerede har fem FormAssembly Connector forbindelser, tilbagekalde eventuelle forbindelser med den laveste brug tæller. Dette vil frigøre en token og hjælpe med at forhindre Salesforce i at tilbagekalde en forbindelse, der stadig anvendes aktivt. Næste, tilbage til FormAssembly. Hover over dit brugernavn i øverste højre hjørne og vælg eksterne tilladelser. Bekræft eventuelle forbindelser markeret som ugyldige. - Hvis du har mindre end fem forbindelser, svæver over dit brugernavn i øverste højre hjørne af FormAssembly og vælge eksterne autorisationer. Så genautorisér eventuelle forbindelser markeret som ugyldige. Hvis du fortsætter med at løbe ind i problemer, bedes du kontakte vores support team.

2. 30. juli 2026 kl. 22.41 UTCmonitoring

   Vi har indsat ændringer, der tager fat på flere medvirkende årsager til problemerne med godkendelse af Salesforce, og antallet af nye rapporter er faldet betydeligt. Vi fortsætter med at overvåge situationen nøje og vil give endnu en opdatering, når vi bekræfter stabiliteten af disse ændringer.

3. 31. juli 2026 kl. 21.38 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. juni 2026 kl. 14.47 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. 5. august 2026 kl. 16.32 UTCresolved

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

1. 16. juni 2026 kl. 19.20 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. 24. juni 2026 kl. 21.47 UTCresolved

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

1. 21. maj 2026 kl. 19.07 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. 20. maj 2026 kl. 15.41 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. 20. maj 2026 kl. 15.43 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. maj 2026 kl. 16.36 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. 20. maj 2026 kl. 18.29 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. 10. juni 2026 kl. 17.52 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. 17. april 2026 kl. 14.09 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. 7. april 2026 kl. 19.35 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. 7. april 2026 kl. 23.56 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. 8. april 2026 kl. 14.49 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. 26. marts 2026 kl. 14.50 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. 26. marts 2026 kl. 15.18 UTCmonitoring

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

3. 26. marts 2026 kl. 15.57 UTCresolved

   This incident has been resolved.

1. 12. februar 2026 kl. 19.10 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. 12. februar 2026 kl. 19.55 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. 12. februar 2026 kl. 20.22 UTCresolved

   This incident has been resolved.

1. 2. februar 2026 kl. 20.27 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. 2. februar 2026 kl. 20.58 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. 4. februar 2026 kl. 20.27 UTCresolved

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

1. 29. januar 2026 kl. 14.51 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. 22. januar 2026 kl. 23.57 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. 23. januar 2026 kl. 19.11 UTCresolved

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