{"version":"2.1.247","anchor":"a-refused-cloud-plugin-change-no-longer-discards-the-setting","canonical_anchor":"a-refused-cloud-plugin-change-no-longer-discards-the-setting","heading":"A refused cloud plugin change no longer discards the settings alongside it","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-refused-cloud-plugin-change-no-longer-discards-the-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A refused cloud plugin change no longer discards the settings alongside it\n\nA refused cloud plugin change no longer throws away the other settings sent with it.\n\n**What**\n\nWhen a cloud settings update carries both a forwarded-plugin change and other settings keys, the plugin part is judged on its own; if it is refused, the remaining keys still apply.\n\n**Details**\n\n- A new event, `tengu_cloud_plugins_mixed_patch`, records whether the plugin part applied, the refusal reason and `sibling_key_count`.\n\n**Evidence**\n\n`tengu_cloud_plugins_mixed_patch`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}