botmux 文档
  • English

      • Delivery when the original topic is unavailable

      topicUnavailablePolicy is a per-bot setting. Configure it under Dashboard → Reply Delivery, or with /botconfig set topicUnavailablePolicy stop.

      ValueBehavior
      legacy (default)Keep existing delivery and fallback behavior without an additional lookup.
      stopCheck the original thread or quote and an explicit destination thread before sending. A withdrawn source blocks delivery, including explicit top-level and alternate destination overrides.

      The setting applies immediately to subsequent CLI sends and automatic final replies. Unthreaded broadcasts have no source topic to check. An already-delivered send that the turn ledger replays performs no new publication.

      TOPIC_SEND_BLOCKED means the queried message is withdrawn. TOPIC_SEND_CHECK_FAILED means the query failed or did not prove the message is available; retry the query on the same route. Neither outcome grants permission to publish elsewhere. A provider-side withdrawal after a successful lookup also prevents the existing quote-to-chat fallback in stop mode.

      Set the value back to legacy, or unset it with /botconfig unset topicUnavailablePolicy, to restore default behavior. This option does not cancel an executing task or prove that its original content should be deleted.

      Each send caches successful lookups for at most one second within that delivery. CLI preparation and the first provider-effect fence each perform a fresh lookup; repeated checks at the same fence reuse that result. Failed or unknown checks are never cached, and the provider withdrawal response still blocks quote fallback.

      CLI refusals use exit code 2 and botmux send refused: …. Permanent withdrawal (including provider code 230011) stops automatic-final retries immediately and marks the session as blocked in Dashboard's needs-you column. The final output remains undelivered; no notice is published to a different conversation.