Recently we had an issue where a job was created by a user and a few months after, it was later amended by a different user. The changes were not saved but no error was displayed and the screen showed the new changes correctly. However after a few minutes (not immediately) the settings reverted to the original resulting in databases not being backed up. We tried changing the settings 5 times and the same thing happened. Ultimately we ended up deleting the job and creating a new one, which worked.
I think at least the software should give an error if the changes cannot be saved (for whatever reason) instead of showing all is fine and making the user believe the changes are saved.
To investigate the issue you encountered we need more information. Could you please enable the Advanced Logs, reproduce the issue, and then send the logs to our development team? Once the log is enabled, try to reproduce the problem so that all necessary information is recorded in logs. Afterward, please send the logs to the developers for analysis.
I haven’t managed to reproduce the issue. The initial jobs that caused the issue were deleted and new jobs created. If it occurs again I will make sure to enable logs and send them.