{"version":"2.1.275","anchor":"plugincommandrun-character-limit-check-silently-removed","canonical_anchor":"plugincommandrun-character-limit-check-silently-removed","heading":"plugin.command.run character-limit check silently removed","tier":"notice","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/plugincommandrun-character-limit-check-silently-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### plugin.command.run character-limit check silently removed\n\nPlugin command.run no longer rejects overly long arguments, only logs their length\n\n**What**\n\nThe check that runs before a plugin's `command.run` operation executes used to reject the call with an error if its arguments exceeded a maximum length. That rejection has been removed: the check now only records the argument length for telemetry (internal usage tracking) and always allows the call to proceed.\n\n**Why**\n\nPlugin commands with very long arguments that would previously have been blocked can now run instead, since the length limit is no longer enforced, only measured.\n\n- Area: Plugin API\n- Names: `command.run`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}