How to Set What Happens When a Backward Job Doesn't Fit in EDGEBIC

To set what happens when a backward job doesn't fit in EDGEBIC, open Settings, go to the Schedule tab, and under "When a Backward Job Doesn't Fit" choose either "Accept the forward schedule" or "Show a popup so I can review it," then click Save. The choice is site-wide policy, it applies to the next scheduling run, and it needs no restart.

Backward scheduling in EDGEBIC by User Solutions places a job just in time, so its last step ends on the due date and spare time sits deliberately in front of the work. Sometimes there simply is not enough free capacity to fit a job before its due date. Backward scheduling never fails outright in that case, because a forward fallback plan (start as early as possible and finish whenever the work allows) always exists. This setting decides one thing only: whether EDGEBIC applies that fallback quietly or stops to ask you first.

Before You Start

• You use backward scheduling. This policy only ever fires for jobs whose direction is Backward. If every job runs forward, the setting never has an effect. See how to set the default scheduling policy.
• You can reach the Settings tab. The Settings navigation tab is permission controlled.
• You understand this is behavior, not data. Nothing is stored on your orders; the setting only changes whether you are interrupted.
• You can run the scheduler. The new behavior applies on the next Drive Schedule run, not retroactively.

Step 1: Open the Schedule Policy Screen

Open the Settings tab from the main navigation. Select the Schedule tab. This screen holds the site-wide scheduling policy: the rulebook the engine reads on every run.

Step 2: Find the "When a Backward Job Doesn't Fit" Group

Scroll to the When a Backward Job Doesn't Fit group. It offers two options:

Step 3: Choose the Behavior You Want

Pick Accept the forward schedule if you value uninterrupted runs and will catch slips on a report. Pick Show a popup so I can review it if a missed promise date must never pass unnoticed. The default is to accept the forward plan silently.

Step 4: Save

Click Save. The status line confirms the change. There is no restart: the next scheduling run reads the new policy.

What Changes When You Save

How to Check It Worked

1. Create or keep a backward job with a due date that is realistically tight against current load.
2. Run Drive Schedule.
3. If you chose the popup, the doesn't fit dialog should appear for that job, showing the earliest possible forward plan. Accept, adjust and re-run, or cancel.
4. If you chose to accept silently, the run completes without a prompt. Open the Late Jobs report and confirm the job appears there if its scheduled end now exceeds its due date.

Common Mistakes

Expecting the popup on forward jobs. The dialog only ever fires for jobs whose direction is Backward. A forward job simply schedules as early as it can and this policy is not consulted.

Thinking the setting can miss a date on your behalf. It cannot make a plan worse. The forward fallback is the same plan you would get either way. The setting only controls whether you approve it in the moment or read about it afterward.

Changing it and not re-running. Policy is read at the next scheduling run. Save, then run Drive Schedule, or nothing appears to change.

Turning on the popup on a rapid-experiment planning station. If your planner runs the scheduler many times an hour, the review dialog will interrupt every tight run. Leave it on accept for that workflow and rely on the Late Jobs report.

Next Steps

This policy is the safety valve on just-in-time planning: decide once whether an impossible finish date should stop you or be caught on a report. Pair it with a deliberate direction choice in how to set the default scheduling policy, and understand the forward fallback itself in forward vs backward scheduling. More single-task recipes live in the EDGEBIC how-to hub, and the platform overview is at /edgebic.