{"version":"2.1.251","anchor":"auto-deny-message-after-a-permission-timeout-is-now-configur","canonical_anchor":"auto-deny-message-after-a-permission-timeout-is-now-configur","heading":"Auto-deny message after a permission timeout is now configurable","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/auto-deny-message-after-a-permission-timeout-is-now-configur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Auto-deny message after a permission timeout is now configurable\n\nPermission timeouts now use a configured denial message, or stay pending if none is set.\n\n**What**\n\nA permission request that times out used to be rejected with a fixed message. The rejection message and behaviour now come from configuration, and if no such resolution is configured the auto-deny is not scheduled at all, so the request simply stays pending.\n\n**Evidence**\n\n`b.denialLimitFallback?.autoDenyResolution`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}