Skip to content

Issue #531: Email task performance improvements and time limit #596

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

Closed

Conversation

Peterburnett
Copy link
Contributor

Closes #531

@Peterburnett Peterburnett force-pushed the issue531-402 branch 2 times, most recently from 84520d8 to 31c296f Compare January 19, 2024 06:06
@Peterburnett
Copy link
Contributor Author

Hi @mdjnelson, just checking in on this one, and if you had any feedback. I can deploy on a fork, but I would rather not where it can be avoided.

It would be ideal if I could include this in my next client deployment in 2-3 weeks

@mdjnelson
Copy link
Owner

Sorry @Peterburnett i've been focusing on other issues and am free to look now. Also, please see there is another improvement for this at #610. Feel free to have a look and comment with what you think. :)

@mdjnelson
Copy link
Owner

Hi Peter,

I don't think it is safe to assume just because the user accessed the course after the last time the task was run that they would have necessarily downloaded the certificate.

What are your thoughts?

@mdjnelson
Copy link
Owner

Closing this in favour of #610 and due to my comments above.

@mdjnelson mdjnelson closed this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CPU % runs high even on an idle server caused by Custom Cert email task
2 participants