{"version":"2.1.227","anchor":"remote-control-config-can-be-read-through-a-storage-backend","canonical_anchor":"remote-control-config-can-be-read-through-a-storage-backend","heading":"Remote control config can be read through a storage backend","tier":"internal","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-control-config-can-be-read-through-a-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote control config can be read through a storage backend\n\nRemote control config can be read through the storage backend, with clearer failure reasons.\n\n**What**\n\nReading the remote control configuration gained an alternative path that goes through a storage backend rather than reading the file directly, classifying the result as text, absent, refused, failed or thrown. Absent maps to an empty config, and failures produce distinct messages that include the backend's error code. Which path a given session takes is not decided anywhere in this build.\n\n**Evidence**\n\n`failed to read `\n\n- Area: Storage Backend\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}