# Event execution order (stop command vs stream play)

**URL:** https://qa.fmod.com/t/event-execution-order-stop-command-vs-stream-play/24495
**Category:** FMOD Studio
**Created:** [September 2, 2026, 1:49pm UTC](https://qa.fmod.com/t/event-execution-order-stop-command-vs-stream-play/24495 "2026-09-02T13:49:17Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)
#### Post date: [September 2, 2026, 1:49pm UTC](https://qa.fmod.com/t/event-execution-order-stop-command-vs-stream-play/24495/1 "2026-09-02T13:49:17Z")

</div>

Studio contains event A (play sound) event B (global stop command → stop all A sounds). If we trigger events B and A in the same frame, we are left with silence. Fmod logs are inconclusive about this…

Flow:

- Game log: both start requests and the stop request were sent.
- FMOD log: stream loading occurred.
- FMOD log: no direct instance-state result.

Is this intended behavior? If I inject flushCommands in between, it works as expected.

---

<div class="post-metadata">

### Author: ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)
#### Post date: [September 3, 2026, 6:43am UTC](https://qa.fmod.com/t/event-execution-order-stop-command-vs-stream-play/24495/2 "2026-09-03T06:43:58Z")

</div>

Hi,

Yes that is the expected behavior. As FMOD Studio works in asynchronously ([FMOD Engine | Studio Api Threads - Studio Thread Overview](https://fmod.com/docs/2.03/api/studio-api-threads.html#studio-thread-overview)) the events are created at the same time, then they are updated at the same time. As the Stop command is for all existing instances of event A it is stopped.

Adding the `FlushCommand()`([FMOD Engine | Studio Api System - Studio::System::Flushcommands](https://fmod.com/docs/2.03/api/studio-api-system.html#studio_system_flushcommands)) will force the Stop command to happen before event A is created so it is allowed to play out:

Without `FlushCommand()`

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/c/c606567f996422b40e4e687152bf6c743444fccc.png)

With

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/e/e39a4bf62e86d278a0a586358572b5d8024fc235.png)

Hope this helps.

---

<div class="post-metadata">

### Author: ![marko.ravnjak](https://avatars.discourse-cdn.com/v4/letter/m/c67d28/32.png) [@marko.ravnjak](https://qa.fmod.com/u/marko.ravnjak)
#### Post date: [September 3, 2026, 6:47am UTC](https://qa.fmod.com/t/event-execution-order-stop-command-vs-stream-play/24495/3 "2026-09-03T06:47:57Z")

</div>

Yeah, makes sense, batching at works 🙂