Hello, Coolaid.
You are correct.
Note though, you can have events defined in the event loop (upper middle on the block diagram) which will en-queue triggers (blue queue wires). For example there is a custom event registration when the TLB' starts up that looks for changes in the front panel and then en-queues "cache user parameters" to the trigger queue. If there is a case for the "cache user parameters" trigger in the present state of the machine (inside case selector on right hand side of the TLB' block diagram) then an action or set thereof may be en-queued to the action queue (which is run by AMC pink queue wires). These actions will be de-queued in the action loop (main loop in the lower middle of the TLB' block diagram) and code held there will be executed to perform the functionality required. You can en-queue multiple actions per trigger if desired.
The idea is that this happens all the time, and so fast that the user doesn't notice any delays.
Best,
James