On Friday, October 9th, we deployed some code that accidentally prevented updates to forms relying on our form handling service. Below is an outline of what happened, and what we’ve done to fix the problem, and what work remains.
If you had a previously working form that was deployed before Friday 9 Oct @ 20:28 UTC, and which you changed by adding, removing, or renaming one more more input fields, between then and now (Wednesday 14 Oct at 17:42 UTC), it is likely we did not correctly process your update, and have not been collecting the visitor-submitted data from those fields since last Friday.
We know that you rely on forms and form inputs, and we’ve been working hard to fix the issue. We have retroactively processed form updates to production deploys on all affected sites, so all of those forms have already begun receiving data for the changed-field submissions.
Please note that we have not re-processed all deploys during that time period, only the current production deploy. However, any other deploy previews or branch deploys with form changes during that time would also have been affected, and can be repaired by you creating a new deploy on that branch or PR (e.g. re-deploying
staging-form on your staging branch that is NOT part of the production deploy). Both new commits or new CLI deploys will trigger the repair-on-redeploy behavior. If you have any questions about how to accomplish this, please ask below and we will advise.
Data from submissions that your visitors have attempted to submit which was in these “missing” (changed) fields was not saved during this time window, and thus cannot be restored. Data in any fields present before Friday was collected and notified about as usual, if submitted.
We want to acknowledge the impact this may have - we never want our customers to have the experience of potentially losing data. We are completing a thorough analysis of what went wrong here, and are taking steps to prevent this from re-occurring.
If you have any questions, concerns, or need clarification on anything, please comment below and we’ll respond as soon as we can.