{"version":"2.1.246","anchor":"plugin-forwarding-to-cloud-sessions-explains-why-nothing-was","canonical_anchor":"plugin-forwarding-to-cloud-sessions-explains-why-nothing-was","heading":"Plugin forwarding to cloud sessions explains why nothing was sent","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/plugin-forwarding-to-cloud-sessions-explains-why-nothing-was","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Plugin forwarding to cloud sessions explains why nothing was sent\n\nWhen your plugins aren't forwarded to a cloud session, you now get the specific reason.\n\n**What**\n\nWhen your local plugin choices are not forwarded to a cloud session, you now get a reason instead of silence: no plugins to send from this machine, your plugin choices here could not be read, they could not be sent this time, or this session is not bound to this machine. The default case nudges you to run the slash command.\n\n**Details**\n\n- The fallback message points at `\/cloud-plugins` to send them manually.\n\n**Evidence**\n\n`run \/cloud-plugins to send them`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}