Manual Flush needed after update and access not allowed

We had (have) various serious problems with different websites with the Redis plugin (or Redis serverside). We use it together with DirectAdmin implementation for Redis ports , most recent!
1. After updating a widget plugin with lay-out (css) problems, we needed a manual FLUSH CACHE to view results. It was fine after that. What is needed in the update process to avoid this?

2. We needed to FLUSH and DISABLE the Redis plugin for WordPress when we use the Duplicator Plugin to move sites between servers. When we did’nt there was a total mess. In fact, the last domain that we acitivated Redis took over the site! Alle errors thus.
Just a transfer of only the database gave great problems and conflicts.

Please have a look at these issues. I like the Redis approach of caching, but it should not lead to extra work and unxpected results.