Troubleshooting
Review draft. This source page has not completed website editorial and release-specific verification.
No runtime context appears
Section titled “No runtime context appears”Start PIE or Game Preview, then select the active World or Game Instance in SignalBus Runtime Inspector. In Multi-PIE, each World and Game Instance appears as its own context.
No event history appears
Section titled “No event history appears”Open Tools → Director Suite → Runtime Controls → SignalBus Runtime Controls and check Diagnostics Enabled for the selected scope. Trigger the event, then refresh the Inspector. Diagnostic capture is a setting on each subsystem context.
A message has no subscribers
Section titled “A message has no subscribers”Confirm that publisher and subscriber use the same message ID, exact reflected payload type, and subsystem scope. Check that the subscription handle remains valid and its lifetime owner is still alive.
A warning returns after clearing
Section titled “A warning returns after clearing”Clear Warnings removes retained records. If warning analysis remains enabled and the triggering condition happens again, SignalBus may create a new warning.
Payload details are missing
Section titled “Payload details are missing”Check Payload Capture in Runtime Controls. The selected policy determines how much payload information future diagnostic snapshots retain; it does not alter the message payload delivered to subscribers.
See Diagnostics and Warnings and Known Limitations for additional detail.