The quick answer
In FactorySync, set the Live Alerts date range and choose Apply Filter. Open Blocked by Previous Operation, then read Blocked by Op, Prev Op Status, and estimated delay across the returned rows. The detail identifies predecessors to investigate. The demonstrated flow shows no save or reschedule action.
FactorySync is a Consule Solutions extension for NetSuite, not a standard Manufacturing Scheduler screen. This guide describes the demonstrated alert, not the extension's general alert rules, delay calculation, or refresh behavior. The screenshots use fictional person and company names and a fictional work order. Your labels, counts, dates, and permissions can differ by installed version and account configuration.
Before you start
You need an enabled FactorySync installation, the role and permissions required by your implementation, and work-order operations that meet the alert criteria. This walkthrough enters March 27 and March 30, 2026 as the start and end dates and follows WO-2044, a Conveyor Frame Assembly order. The recording demonstrates a read-only diagnosis. Check current work-order progress and the actual production schedule in your account before changing dates or assignments.
01. Open Live Alerts
Open FactorySync and locate the floating Live Alerts widget above its Capacity Planning view. The widget has two date inputs, an Apply Filter button, and separate shortage, blocked-operation, and overdue categories. These are the extension's controls.
02. Filter the alert dates
Enter 03/27/2026 and 03/30/2026 in the Live Alerts date inputs, then choose Apply Filter. In this example, Blocked by Previous Operation shows three alerts. The shortage and overdue counts are separate categories; they do not explain this work order's predecessor chain.
03. Open blocked operations
Choose Blocked by Previous Operation. A detail dialog opens with work order, item, operation, work center, status, predecessor, previous-operation status, scheduled start, estimated delay, and due date. The demonstrated click opens a diagnostic list; no save or work-order update is shown.
04. Trace the predecessor
Read every WO-2044 row across. Operation 20 at Hydraulics Shop is NOTSTART, blocked by operation 10, whose previous-operation status is also NOTSTART. Its estimated delay is +9 days. Operations 30 and 40 point to predecessors 20 and 30 and each show +5 days. These rows form a predecessor sequence in this example; other multi-row results may differ. The displayed delays are extension estimates, not confirmed new completion dates. The replay does not establish their calculation or refresh timing. Investigate the referenced operations and current schedule to decide what, if anything, needs to change.
Check the result
- The affected work order appears in the blocked-operation detail.
- Its first blocked row names the predecessor and previous-operation status.
- Any schedule decision is checked against current work-order progress; no saved change was shown in this flow.
Common questions
Is Live Alerts part of standard NetSuite manufacturing?
No. The screens here belong to the FactorySync extension. A standard NetSuite account may show different scheduling and work-order pages and may not have this alert widget.
What does “Blocked by Op” tell me?
In this dialog, it names the earlier operation the alert associates with the blocked row. Read Prev Op Status alongside it, then verify that operation's current progress in your account.
Does the estimated delay change the work-order due date?
The demonstrated flow shows no saved date change or reschedule. The displayed delay is an extension estimate; the recording does not establish how it is calculated or prove that it updates a due date.
Why are several operations from one order listed?
The example shows a sequence: operation 20 points to 10, operation 30 points to 20, and operation 40 points to 30. Other multi-row results may represent different blocks. Confirm the actual dependencies and schedule before acting.