Caching profile objects led to unwanted behaviours because of stale data

Problem/Motivation

I have two scheduled tasks with two different local destinations each (one for databases and one for files), and both backups where ending up in the same destination.

Proposed resolution

After debugging for hours and hours and realised that this was because of stale data in the profile object. The schedule loads a profile, but then the profile is modified and loaded with data across the different functions, and once the next schedule is loaded, the schedule in turn load the profile and because the profile have all of the stale data from previous run the destinations are not reset.

Looking at the code I really think profile data should not be cached, caching it could potentially led to a lot of difficult to spot issues, like this one. I project wise search the use of this function and it's used very seldom. Removing the case will pose little to none performance hit.