The Anomaly Report Flags a Job I Think Is Fine

Not every anomaly row is a defect. Warning-level checks flag normal schedule texture, some findings are advisory rather than errors, and a report run against stale data can flag a job you already fixed. The severity label and the check identity tell you which kind you are looking at, so EDGEBIC by User Solutions lets you separate the false alarms from the real problems in seconds.

This post is part of the EDGEBIC troubleshooting guide. It explains the severity split, which findings are expected in a healthy plant, and how to confirm a flagged job really is fine.

Severity Is the First Signal

Every finding in the scheduling anomaly report carries a severity. That single label is the fastest way to decide whether a row deserves your attention.

Critical findings are the ones that break a schedule: over-booking a machine past its physical day, running one instance on two jobs at once, an inverted or zero-length window, a reference to a deleted machine. Those are never fine. Warnings are different. Many of them describe normal schedule texture, and the health target for a production plant is zero Critical rows, not zero rows of any kind.

The Findings That Are Usually Fine

Three families of warning are expected in a healthy schedule.

Idle gaps between jobs. A gap over a small threshold between two jobs on a machine is reported, but most gaps are explained by buffers, shift boundaries, or another job. The idle-gaps sibling covers when a gap is genuine waste and when it is protection.

Routing hours drift. When a schedule's booked hours differ from what the routing currently says, the drift finding fires. That difference is expected when you changed the routing after scheduling, or when the job ran on an alternative machine with a speed factor. It is a Warning precisely because it is often intentional. Re-run scheduling and it clears if the drift was just a stale routing.

Dead-field and advisory notices. A value sitting in a field the scheduler does not read produces a dead-field warning: harmless, but worth cleaning up. Advisory findings about ambiguous overlap or transit configuration mean the schedule is valid and deterministic; they are asking you to confirm your intent, not reporting a defect. What the EDGEBIC anomaly checks actually look for covers the full catalog.

The Dependent-Parallel Exception

One specific case trips people up. A dependent parallel machine mirrors its parent exactly, so it legitimately emits hours that exceed a single machine's shift window. The shift-design over-utilization warnings exclude these mirrors by design, so an excluded-category warning on a mirror is expected.

The exception to the exception: if a physical over-utilization Critical fires on a mirror, that is real. It means the mirror's factor times the parent's hours exceeds the physical day for the instance count. That is a constraint the factor or the instance count needs to resolve, not a false positive. Read the severity to tell them apart.

Confirm With a Fresh Report

The report reads the current stored state. If you changed master data and re-ran scheduling but opened a report from before that run, it shows the old anomalies. The routine that removes this doubt:

1. Re-run scheduling for the job in question.
2. Open the anomaly report immediately after, filtered to that job. See how to run and read the anomaly report.
3. Read the severity and the check identity on any surviving row.
4. If a Critical survives, it is real. If only Warnings survive, judge each against the expected list above.

A finding that disappears on a fresh run was stale. One that persists is worth the attention its severity implies, and when a row survives a correction you know you made, an anomaly row that outlives the fix explains why the report reads stored state. When several checks fire on one job, work the Critical rows first: fixing the root often clears the dependent Warnings automatically, which is the pattern behind why a job jumps after a reschedule. The troubleshooting guide links the specific checks.