Sounds like a poor firmware/software design by Reolink. It may be buggy, unintuitive, or incorrectly implemented (or all of the above) -- hard to say without more info.
But I'm glad it is now resolved.
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks! 