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

Move Async Email Actionlet to Core #28360

Closed
jdotcms opened this issue Apr 25, 2024 · 1 comment · Fixed by #28361
Closed

Move Async Email Actionlet to Core #28360

jdotcms opened this issue Apr 25, 2024 · 1 comment · Fixed by #28361

Comments

@jdotcms
Copy link
Contributor

jdotcms commented Apr 25, 2024

Parent Issue

No response

Task

As an user I want to decide if I want to use the async email or the normal one to send emails.
Currently the async is a plugin for client having issue with the slow stmp (email took 15 seconds to be sent)
and this stops the workflow until the email is being send
For those cases, the alternative would be to use the async email

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

Acceptance Criteria

The Async email should be on the available actionlets

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

This is already working for clients, it is just copy/paste from the plugin

Sub-Tasks & Estimates

No response

@jdotcms
Copy link
Contributor Author

jdotcms commented Apr 25, 2024

Evidence about how it is working
Screenshot 2024-04-25 at 1 19 25 PM
Screenshot 2024-04-25 at 1 19 15 PM

github-merge-queue bot pushed a commit that referenced this issue May 9, 2024
* #28360 migrating the async email to core

* #28360 adding refactor for sonarq feedback

* #28360 adding refactor for sonarq feedback

* #28360 adding refactor for sonarq feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Internal QA
Development

Successfully merging a pull request may close this issue.

1 participant