# \[IGN-18293\] Form Submit Button

**URL:** <https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245>\
**Category:** Ignition\
**Tags:** perspective, scripting\
**Created:** [September 29, 2026, 3:41pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245 "2026-09-29T15:41:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sabeeha.hazmi](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sabeeha.hazmi](https://forum.inductiveautomation.com/u/sabeeha.hazmi)\
**Post date:** [September 29, 2026, 3:41pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245/1 "2026-09-29T15:41:13Z")

</div>

I am using ignition version 8.3.7. I have a Form component with the submit button configured to trigger a run of a onSubmitActionPerformed script. This is how my submit tree look like currently in designer:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/c/7c23c026f87db84def5b2427db01b13b84f405de.png)

However, when I launch the project and click submit with all the form fields filled out properly, the submit script is not triggered. I have to reload the project launch web page and then click submit in the form for the submit action script to be triggered. I am confused on why this problem might be. Does anyone have an idea/suggestions I can try out?

---

<div class="post-metadata">

**Author:** ![ptshaw](https://avatars.discourse-cdn.com/v4/letter/p/3be4f8/32.png) [@ptshaw](https://forum.inductiveautomation.com/u/ptshaw)\
**Post date:** [September 29, 2026, 5:53pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245/2 "2026-09-29T17:53:53Z")

</div>

Do you have any restraints on the questions/widgets? I have also encountered an issue occasionally where my submit button remains disabled even though all required questions were answered. This might be the same issue but my configuration has "autoDisable" set to True. Just wanted mention that you may not be alone on this one.

Also have some other form related issues, but not sure if bugs or just general lack of knowledge on my end. I won't hijack your thread though.

---

<div class="post-metadata">

**Author:** ![ptshaw](https://avatars.discourse-cdn.com/v4/letter/p/3be4f8/32.png) [@ptshaw](https://forum.inductiveautomation.com/u/ptshaw)\
**Post date:** [September 29, 2026, 6:12pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245/3 "2026-09-29T18:12:32Z")

</div>

I have noticed that if I hit cancel to reset the form and fill it out again it will work correctly. Not a real solution but something to try.

---

<div class="post-metadata">

**Author:** ![sabeeha.hazmi](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@sabeeha.hazmi](https://forum.inductiveautomation.com/u/sabeeha.hazmi)\
**Post date:** [September 29, 2026, 9:07pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245/4 "2026-09-29T21:07:50Z")

</div>

I do have restrains on the questions on the forum where some appear when certain options are selected in prior questions. However, those are all independent of the submit as long as they answer all the required fields. I do put something in all the fields before I try submitting.

I checked the autoDisable and its set for False, and FireSubmissionEvent also set to False.

the cancel button works fine, however it does not help me click the submit button like it does for you.

For more context, I do have a file upload component added onto the same parent container:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/a/5a5db6915941073dcf8f613085f5bc0ae75b5d68.png)

---

<div class="post-metadata">

**Author:** ![pamato](https://avatars.discourse-cdn.com/v4/letter/p/c68b51/32.png) [@pamato](https://forum.inductiveautomation.com/u/pamato)\
**Post date:** [October 13, 2026, 2:51pm UTC](https://forum.inductiveautomation.com/t/ign-18293-form-submit-button/117245/5 "2026-10-13T14:51:09Z")

</div>

@sabeeha.hazmi I've looked into what you may be experiencing and found an issue in certain scenarios with the timing of events and form state. I filed a ticket to get this addressed.