video1.0<iframe src="https://www.loom.com/embed/44847c8e4f1b4697b9302d79079089dd" frameborder="0" width="1658" height="1243" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12431658Loomhttps://www.loom.com12431658https://cdn.loom.com/sessions/thumbnails/44847c8e4f1b4697b9302d79079089dd-a8da689225738124.gif210.304This Loom explains how a system automatically monitors Slack conversations and Linear data to match tasks and surface blockers. It demonstrates that items can appear mismatched, such as Slack conversation work not matching a Linear ticket, which leads to gaps like an unresolved blocker until the API team provides the needed API access. The speaker notes that some work is blocked waiting for API access, while other conversion references show no matching Linear ticket. The system is described as finding differences and notifying users about issues in company workflows.