-
Notifications
You must be signed in to change notification settings - Fork 26
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
Recursion error in periodic data removal #2632
Comments
@joeribekker I'd like to make a case again for snapshotting the entire state/configuration of the form inside the submission so we can get rid of this less-than-optimal historical step configuration workaround, it's unpredictable |
I agree this can be one of the big topics, but seems less urgent than others. |
I'm afraid this bug is causing submissions to not be deleted at all when it occurs, iv'e checked multiple instances and the rules set in the general config don't seem to apply anymore for all instances where this bug occurs. |
Alright, prio re-evaluated. I need someone to explain to me how this works and @sergei-maertens how much work the state-save means. |
Refinement: Timebox this on 1 day to see if we can have a bandaid fix for this that at least doesn't break the entire task so nothing gets cleaned up. If not possible, we go for the full solution (inform us in the next refinement): Keep the state of forms properly in the submission. |
+ preliminary 'fix' by catching the recursion error
I've found a bandaid fix :) |
…rror [#2632] fix recursion error
Product versie / Product version
All
Sentry 321138
Omschrijf het probleem / Describe the bug
Error can be found in Sentry. Originates from delete_submission and can be found in all deployed instances
The text was updated successfully, but these errors were encountered: