If it detects any Source changes, it will probably run again (as per the Help, it almost certainly won't detect changes on the Destination if that is a NAS). The profile doesn't (always) run in the background with OnChange, but the program does (unless you close it, obviously - if so , change-monitoring will stop) and monitors Windows' alerts re folder\file changes, and triggers the profile if appropriate to its scope.
And/or you can run it manually to pre-empt that detection.
But whether the Critical errors would re-occur or be solved rather depends on what they actually are (that is, suggest read/quote the error messages in the log). You should probably also read the Warnings, or we're wasting our time logging them (note that Warnings do not set the Result as a Failure, but critical Errors do)
And/or you can run it manually to pre-empt that detection.
But whether the Critical errors would re-occur or be solved rather depends on what they actually are (that is, suggest read/quote the error messages in the log). You should probably also read the Warnings, or we're wasting our time logging them (note that Warnings do not set the Result as a Failure, but critical Errors do)
