Lifespan submissions not equalling to submission count

  • I regularly have forms for event registrations (with paypal) which are limited to an amount which i set in the Behaviour section – Lifespan – Submissions. Eg i set to 56 on the latest form.

    The form however has closed at 54 submissons. From my checking in the database 56 entry_id are recorded against the form_id and I have located the two which are not showing. Both of these have no entries in the entry_meta table which leads me to think these were completed forms but payment was not completed and so they didnt register as a full submission and hence no form data saved. If this is a case why does it log an ID taking up a submission which counts towards my lifespan maximum and is there a way to avoid this?

    • This topic was modified 1 day, 15 hours ago by all3design.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Saurabh – WPMU DEV Support

    (@wpmudev-support7)

    Hello @all3design

    Hope you’re doing well today! Thanks for reaching out to us.

    I have pinged the Forminator team about the issue you noticed to gain some additional insights about the expected behaviour in case of failed payment/incomplete payment.

    We will update you here as soon as we receive additional insights about this from the Forminator team.

    Thank you for your patience.

    Kind Regards,
    Saurabh

    Plugin Support Saurabh – WPMU DEV Support

    (@wpmudev-support7)

    Hello @all3design

    An update here,

    I have further insights from the Forminator developers, and what you noticed is an expected behaviour with forms having payment fields.

    To explain further, the first step Forminator does is to create a new submission as it requires the Submission ID for the next steps like make a request to the Payment gateway to charge the request. In case while the request is being made, and if fails it will have a saved submission (hence the ID taking up a submission).

    In short, the submissions kind of “wait” to fetch the payment confirmation status and removing them is a bit risky as it can be paid later. Hence, at the moment there isn’t any workaround to avoid this situation I am afraid.

    However, since the developers have made a note of it, we’ve already created an improvement task to explore it further so that the handling can be improved.

    That said, at the moment I cannot confirm an ETA as to when the fix will be released. In this case I would recommend you to follow our roadmap https://wpmudev.com/roadmap/ so that you are notified when we release an update.

    Apologies for the inconvenience caused.

    Kind Regards,
    Saurabh

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.