I'm receiving duplicate, delayed notifications of form submissions

  • Profile Image
    Asked on June 18, 2021 at 11:08 AM

    I'm receiving random duplicate notifications of form submissions, both from the Jotform app as well as by email.

    It makes it appear as though the person completing the form has completed it again with the same information.

    The duplicate notifications often occur 2-3 days after the original submission, and not every form submission is duplicated. It seems random.

    This is happening just often enough to cause problems with responding to the requests we receive via our jotform.

    So what is triggering jotform to respond as if a form submission has just occurred, using a random previous submission?

  • Profile Image
    Answered on June 18, 2021 at 04:13 PM

    Hello! 👋

    Thanks for reaching out! Could you provide us with the form URL that you're experiencing this with? This will help us investigate this further.

    What could be happening is that the user / form owner are editing the submission. If Send email on form edited is checked in your Notification or Autoresponder settings in your form builder than you will receive an email email every time the submission is edited.


    If you have any other questions or have any additional information, please let us know!


  • Profile Image
    Answered on June 20, 2021 at 06:33 PM
    Thanks for your response, here is the URL:
    Based on your suggestion below, I have turned off "send email on form
    edited" in case that's the problem - but as far as I know, none of my users
    have or would edit an existing form.
    Mathew Raikes
    (505) 615-3047
  • Profile Image
    Answered on June 20, 2021 at 09:36 PM

    Hi Mathew, thank you for giving my colleague's suggestion a try.

    After you have turned off the "Send email on form edited" option, does the issue still persists?

    If the issue still persists, kindly let us know if the form is embedded somewhere else. Please provide us with the website URL where the form is embedded too.

    If the issue no longer persists, I suggest trying my colleague's suggestion the next time a similar issue arises on a different form.