-
Notifications
You must be signed in to change notification settings - Fork 7
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
Mailchimp list is not updated automatically for new members #33
Comments
It is. The ORM object is expiring in between form submission and worker operation. I think passing the generated ID (after the entry is committed to the DB) to the worker and letting the worker re-request the object in a new session (using that ID - which is just an int) is how we can fix this. |
That could work, but why would it be expiring? I'd imagine the worker processes incoming items almost instantly. |
Yes, but it's not the same session. The instances are attached to the session they were created in. |
#34 did not adequately fix the issue, most likely because the fields are not populated before being expunged. |
It works when testing initially so maybe it only breaks after running for a period of time.
I suspect an unhandled exception is killing the Mailchimp worker. It could be related to this SQLAlchemy error:
The text was updated successfully, but these errors were encountered: