{"version":"2.1.228","anchor":"slack-ping-origin-plumbed-through-message-handling-but-nothi","canonical_anchor":"slack-ping-origin-plumbed-through-message-handling-but-nothi","heading":"Slack ping origin plumbed through message handling, but nothing creates one","tier":"soon","area":"Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/slack-ping-origin-plumbed-through-message-handling-but-nothi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Slack ping origin plumbed through message handling, but nothing creates one\n\nMessages can be tagged as coming from a Slack ping, but nothing in this build creates one.\n\n**What**\n\nA new message origin kind for Slack pings is wired through message display, prompt queueing, system-reminder wrapping and harness tag neutralisation, with its own equality check over channel, thread, message, Slack user, sender name and permalink. No code path in this build produces an origin of this kind.\n\n**Details**\n\n- A Slack origin field is passed from the inbound bridge payload into the origin classifier, which currently ignores the argument\n- The classifier's two Slack observation checks are hard-coded to return false\n\n**Evidence**\n\n`slack-ping`\n\n- Area: Messaging\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}