# MSO Python API and digital triggers

**URL:** <https://discuss.saleae.com/t/mso-python-api-and-digital-triggers/3690>\
**Category:** Logic MSO\
**Created:** [April 13, 2026, 8:24am UTC](https://discuss.saleae.com/t/mso-python-api-and-digital-triggers/3690 "2026-04-13T08:24:14Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [October 14, 2026, 8:13pm UTC](https://discuss.saleae.com/t/mso-python-api-and-digital-triggers/3690/5 "2026-10-14T20:13:37Z")

</div>

@andrej.nussdorfer Thanks for checking in on this. Our latest update on this topic can be found here.

> [@One shot digital triggers](https://discuss.saleae.com/t/one-shot-digital-triggers/3667/8):
>
> Hi @durian, It’s still in work, and we actually added single-shot digital trigger to the new headless API for Logic MSO: [Headless logic2-automartion support for Logic MSO!](https://discuss.saleae.com/t/headless-logic2-automartion-support-for-logic-mso/3798) Under the hood, we’re replacing the data processing pipeline for MSO, in order to fix the underlying issues that were blocking single shot digital trigger. The new headless API is already using that new pipeline, but there is a lot more work left to do in Logic 2 to switch over to it. We were supposed to be working on that t…

---

_[View the full topic](https://discuss.saleae.com/t/mso-python-api-and-digital-triggers/3690)._
