| Previous | Next |
| STATUS_FWP_TOO_MANY_CALLOUTS | STATUS_FWP_TRAFFIC_MISMATCH |
STATUS_FWP_NOTIFICATION_DROPPED
An event was lost at delivery time
STATUS_FWP_NOTIFICATION_DROPPED means the filter engine could not deliver a notification because the receiving message queue reached its capacity. It does not establish that the underlying add, delete, or classification event failed; it establishes that the observer missed a notification.
A notification consumer should therefore treat this status as a resynchronization boundary. Re-enumerate the relevant object class or obtain the current policy snapshot before relying on incremental notification state. Simply increasing logging after the fact cannot reconstruct an event that was not delivered.
What to measure
- Notification producer rate, callback/service processing time, and queue pressure.
- The object classes covered by the subscription and the last confirmed state.
- Whether the consumer performs a full refresh after a dropped-notification signal.
- Back-pressure or batching behavior in the component that consumes updates.
References
- Microsoft: WFP error codes
- Microsoft: WFP sessions, transactions, and object lifetimes
- Microsoft: WFP object model
Looking for a different code? Search another status or error code.