-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submission Error: Maximum execution time of 30 seconds exceeded #1783
Comments
This is happening on more than one project when upgraded to 5.9.7 from a prior version. |
I'm very sorry for the trouble you're experiencing @vonscriptor, I cannot duplicate this issue and haven't heard of this being reported yet. Would you be able to provide the following? 🙂
Thanks! |
Just to reiterate this happened on 2 of my projects that I just attempted to update Freeform on. One uses Freeform Pro, the other uses Express. Both updated from the same versions (5.8.7). Both timed out, huge stack trace gets output, ends up slowing down my server(s) for a bit after the timeout even. No integrations on the simple Express project. |
Sorry forgot to mention… those are screenshots after downgrading Freeform back to v5.8.7. Thought it'd still be what you're looking for. |
Thanks @vonscriptor, I am having a developer check into this shortly. 🙂 |
This should now be resolved in Freeform 5.9.8+ 🙂 |
Looks like maybe your environment isn't liking a number of files. We'll check into this again shortly. |
Reviewing this again, I see that the files you reference are not part of Freeform. Can you share the full stack trace of the error you get to see where/if Freeform is causing the issue? 🙂 Thanks! |
The only way I'm able to get a Freeform submission to work is by disabling "Store Submitted Data for this Form". The Notifications will work as normal. I tried creating a new form with one default text field and a submit button, AJAX / no AJAX, no notifications, no rules, no integrations. Disabling "Store Submitted Data for this Form" was the only way for me to get around the timeout. The timeout is inconsistent in what it reports. My uninformed guess would be because when Freeform tries to store the submission in the database it's causing Craft to attempt things over and over until it the timeout and the stack trace is just where it was in the process at that moment. Here are 2 times in my testing just now that showed a stack trace with Freeform:
Hopefully this is helpful! Let me know what else I can do. Thanks! |
Thanks @vonscriptor. However, would you be able to copy and paste the entire thing? 🙂 |
Just sent a support email. When you reply I can attach a bunch of screenshots for reference. |
Can you share the contents of |
Can you edit this file locally: Just before line #19, add Tell me what outputs please? I want to see what $attribute is coming back as? |
@seandelaney I do have /web/dist/js/freeform-recaptcha_v3.js (and a .js.gz), but is this being used?
When adding If I put it before the |
@vonscriptor Is this for a form that is causing max timeout errors? I want to try and catch what the $attributes are when the error triggers. |
What happened?
When submitting a form it times out with the error:
Maximum execution time of 30 seconds exceeded.
This started occurring after an update from v5.8.7 to v5.9.7.
Errors and Stack Trace (if available)
How can we reproduce this?
I'm not really sure how to reproduce this.
Freeform Edition
Pro
Freeform Version
5.9.7
Craft Version
Pro 5.6.5.1
When did this issue start?
After upgrading from older Freeform version
Previous Freeform Version
5.8.7
The text was updated successfully, but these errors were encountered: