Best practices for monitoring Load Entity Warnings during Data Collection

Summary:

We are planning to run a nightly Targeted data collection from Fusion.

The Collection Job Set completes successfully even when one or more Load Entity child jobs finish with Warning. Some warnings require investigation, while others are expected and can typically be ignored, such as warnings generated during Units of Measure, Supplier Site, and Planning Attribute Values collections.

How do other customers typically monitor and review Load Entity warnings? Is there a recommended best practice for distinguishing warnings that require action from those that can be safely ignored?

Since the Collection Job Set itself completes successfully, we are particularly interested in how customers incorporate this review into their daily operations.