DevTools
Diagnose queues and Policies
Determine whether a Command was delayed, displaced, rejected, serialized, restarted, or cancelled.
v0.1.0-dev.3Advancedusecase_forge_devtools
Open source reference ↗Diagnose queues and Policies
Begin at the earliest visible boundary:
- Check rejection reason before inspecting handler timing.
- Compare the exact Command type and execution key.
- If the Entry remains in Admission, inspect Debounce, Throttle, Rate Limit, conflict Policy, and queue capacity.
- If it remains Pending, inspect Execution mode and related active work.
- If it reached Processing, follow cancellation, error, and terminal events.
Common signatures
| Evidence | Likely explanation |
|---|---|
repeated debounced | a newer keyed candidate replaced the previous trailing candidate |
repeated throttled | Commands arrived inside the active throttle window |
rateLimitExceeded | the sliding window already contains the configured maximum |
inputConflict | rejectNew found related waiting work |
activeConflict | processing rejectNew found a related active Execution |
| cancelled, then a new start | restart cooperatively displaced active work |
The screen reports what the runtime observed. It cannot establish whether a Policy is correct for the product requirement; that decision remains in application design.