diff --git a/issues/mediacapture-handle-actions-missingtask.md b/issues/mediacapture-handle-actions-missingtask.md
new file mode 100644
index 0000000..c717417
--- /dev/null
+++ b/issues/mediacapture-handle-actions-missingtask.md
@@ -0,0 +1,16 @@
+---
+Title: >-
+  [mediacapture-handle-actions] Missing tasks in parallel steps in The
+  Capture-Handle Actions Mechanism
+Tracked: N/A
+Repo: 'https://github.com/w3c/mediacapture-handle'
+---
+
+While crawling [The Capture-Handle Actions Mechanism](https://w3c.github.io/mediacapture-handle/actions/), the following algorithms fire an event, or resolve or reject a Promise, within a step that runs [in parallel](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel) without first queuing a task:
+* [ ] The [MediaStreamTrack/sendCaptureAction()](https://w3c.github.io/mediacapture-handle/actions/#dom-mediastreamtrack-sendcaptureaction) algorithm resolves/rejects a promise directly in a step that runs in parallel
+
+See [Dealing with the event loop](https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-for-spec-authors) in the HTML specification for guidance on how to deal with algorithm sections that run *in parallel*.
+
+<sub>Cc @dontcallmedom @tidoust</sub>
+
+<sub>This issue was detected and reported semi-automatically by [Strudy](https://github.com/w3c/strudy/) based on data collected in [webref](https://github.com/w3c/webref/).</sub>