Not everything in the log is equally serious. DataMergeStudio separates errors from warnings.
An error means something couldn’t be done – a required value was missing, an image couldn’t be found – so a record, or the run, couldn’t complete as intended. Errors are what you resolve before trusting the output.
A warning is worth knowing but didn’t stop the merge: something fell back to a default, or looked unusual. Review warnings, but they aren’t blockers.
It lets you triage. Clear the errors first – they affect the result – then decide whether the warnings need action. A run with only warnings may be perfectly fine to ship.
Go straight from an entry to its cause: Jumping from the Log to the Problem