The Gantt Is Blank After a Run: Display, Data, or a Failed Run

A blank Gantt after a run is far more often a view hiding a good schedule than a run that produced nothing, and the two are quick to tell apart: look at whether scheduled operations exist behind the view before you touch any setting. Three view causes and two real ones cover it, and the view causes are both the most common and the cheapest to rule out.

EDGEBIC by User Solutions keeps the schedule in the data regardless of what the Gantt is showing, so an empty timeline is a question about the view and the run, not about lost work. This post is the detailed version of the "the screen looks wrong, not the schedule" symptom in the EDGEBIC troubleshooting guide.

First: Is There a Schedule Behind the View?

Before adjusting anything, establish which situation you are in:

• The order list shows scheduled jobs, and only the Gantt is empty. This is a view problem. Widen the window, clear filters.
• The failure dialog listed every job, and none scheduled. The run genuinely produced nothing. The fix is in the failure reasons, not the view.

That single check saves you from resetting layouts to chase a run that never placed anything. The order list and the failure dialog together answer it in seconds.

Cause 1: The Date-Range Window Excludes Everything

The Job View filters to a start and end date range. If that window ends before the scheduled work begins, or begins after it ends, the Gantt shows nothing even though the schedule is intact. This is the most common cause of a blank timeline after a clean run, especially when the scheduled work lands weeks out.

How to tell: the run succeeded, the order list shows jobs, and the date window is narrow or points at the wrong period.

Fix: widen the date range generously and look again. Clearing either end of the range falls back to the job's own bounds, which is a safe way to see everything the job scheduled.

Cause 2: The Job Filter Has Everything Unchecked

The Gantt's job filter can hide jobs by unchecking them, and the filter persists with your saved layout. If every job is unchecked, or the ones you want are, the timeline is empty by request.

How to tell: the job filter list shows unchecked jobs where you expected checked ones.

Fix: re-check the jobs, or reset the layout to clear the saved filter. The settings offer a one-click reset of all layouts to defaults, covered in the settings that change how your schedule looks.

Cause 3: Inverted Actual Dates Blanked the View

This is the one view symptom that is actually a data problem wearing a display costume. If any operation ends up with an end time at or before its start time, the display cannot draw that bar, and the safeguard that normally prevents this can be defeated by imported data carrying inverted dates. The result is that the whole view goes blank, not just the one bar.

How to tell: the Gantt was fine, then you imported or edited actuals, and now it is entirely empty. The anomaly report's inverted-actuals check names the offending operation.

Fix: correct that operation's actual dates so the end is after the start, entered through the actuals surface, which validates the pair on write. Once the bad row is fixed, the Gantt renders again. Bars that come out blank on one machine rather than across the whole view are a different reference problem, covered in a deleted machine instance that left a schedule broken. Log actual hours and pieces covers the correct entry path, and actual dates look wrong covers tracing bad actuals in general.

Cause 4: The Run Actually Produced Nothing

If the failure dialog listed every job, the run placed nothing, and the empty Gantt is honest. This is not a view problem.

How to tell: the failure dialog shows every submitted job as failed.

Fix: address the failures. A whole run that produces nothing usually shares one root cause across the jobs, most often a master-data gap like missing shifts or a missing routing, so fixing one often clears many. A job that will not schedule covers the failure categories.

Cause 5: The Wrong Sub-Tab or View Mode

The Schedule area has several views of the same underlying plan. A view that looks empty may simply be a mode showing a different slice, or one you have not populated the way you remember. Comparing what you recall from one view against what you are reading in another is a classic source of a phantom empty screen.

How to tell: another view of the same schedule shows the work.

Fix: confirm you are on the view you think you are, then apply the window and filter checks to that view specifically. If the bars are drawn but nothing sits under them, a scheduled operation showing no assigned resources covers the resource detail the last run did not build.

The Diagnostic, in Order

1. Order list shows jobs? If yes, it is a view problem; continue. If no, read the failure dialog.
2. Widen the date range. Most common view cause.
3. Clear the job filter or reset the layout. Second most common.
4. Did you just import or edit actuals? Check the anomaly report for inverted dates and correct the named operation.
5. Confirm the view mode. The right schedule can hide behind the wrong tab.

Prevention

• Keep the date range wide during normal work, and narrow it deliberately only when you want a focused window. A too-narrow default is the quietest way to blank a good schedule.
• Reset the layout when a view looks wrong before assuming a scheduling fault. Ten seconds of display hygiene beats an hour hunting a bug that is not there.
• Validate imported actuals for inverted dates. The anomaly report's inverted-actuals check is the fast way to catch the one data problem that can blank the whole timeline, ideally before the Gantt does.
• Read the failure dialog on every run. A run that produced nothing is a failure story, and the dialog holds the reasons; an empty Gantt is the symptom, not the cause.