-
Notifications
You must be signed in to change notification settings - Fork 74
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
removing a failing system and integration will still cause a request to fail #3769
Comments
after doing some initial investigation, it's worth noting that this isn't even specifically tied to reprocessing an existing privacy request. this seems to impact any new, future privacy request too. this implies a bigger impact to users, and also a different root cause technically - it doesn't have anything to do with request reprocessing, it's some artifact from the deleted system/integration being left around generally, not something tied to a particular request state. |
on first glance, it looks like the problem here is that both the in at this point it's probably worth clarifying expectations, since i do notice that the "old" connection still exists in the "connection manager" screen. do we expect deleting a system to effectively also delete its integration, or should users have to go into the connection manager and explicitly delete the integration? if it's the former, then i think we'll need to update the system delete operation to remove these "integration" artifacts from the db (either by making multiple API calls from the FE or adjusting the API on the BE. |
They won't be able to use the connection manager anymore so, yes, deleting a systems should delete the connection/integration. |
moving to done |
Bug Description
even after removing a failing system and integration will still cause a request to fail
Steps to Reproduce
Expected behavior
the request still errors on domo
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: