Skip to content
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

Add option to process specific integrations immediately rather than in the queue #1152

Open
Mosnar opened this issue Oct 28, 2022 · 3 comments
Milestone

Comments

@Mosnar
Copy link
Contributor

Mosnar commented Oct 28, 2022

What are you trying to do?

I'm using the element integration to power a user registration form. I think it would be more ideal if this integration ran immediately. This would solve two issues:

  • Element validation errors could be accounted for during the form submission validation. This prevents errors related to required user fields that aren't present in the registration form.
  • Verification emails and critical event listeners avoid being trapped behind a potentially full or stalled queue worker. If I register, I expect to get a verification email immediately, not in 15 minutes when Craft finishes pruning revisions.

Related: #1151

What's your proposed solution?

Add a generic option to integration settings to "Process Immediately", which would direct Formie to execute the integration immediately rather than pushing it to the back of the line.

Additional context

No response

@Mosnar Mosnar changed the title Add option to not process integrations for a particular form in the queue Add option to process specific integrations immediately rather than in the queue Oct 28, 2022
@engram-design
Copy link
Member

engram-design commented Oct 28, 2022

Yeah this is a pretty valid use-case I suppose, and while not ideal, not really any way around it other than processing it outside of the queue (or proving the option to do so).

As for validation, that's tricky, because integrations (and email notifications) are done after a submission is successful, so it would need to back-track a successful submission to make it invalid is an error was encountered in the integration.

@engram-design engram-design added this to the 2.1.x milestone Oct 28, 2022
@a-am
Copy link

a-am commented Feb 16, 2023

I have also run into this issue. When creating registration a user is unable to login directly after registration. They can't login until the queue is run.

@jishi
Copy link

jishi commented May 2, 2023

I have run into a similar problem here. I'm using a form to create Entries (pages) and the problem is two-fold:

Entry might not exist when you are at the success page of the form submit.
There is no way to actually link to the newly created Entry form a success page, nor in an email notification, which might be preferable.

The second problem might be solvable by allowing email notifications to be triggered when all integrations (or at least one) are finished, but maybe that is not possible the way the queue system works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants