When the user rotates the “session api key”, what should the behavior be? From what I know, please correct me if wrong, unfortunately sdk and automation encrypt with the old key, and have no awareness of a key change. So they error out, because nothing can be decrypted anymore. Alternatives: • implement the secrets redesign, it’s clean then • keep the old key too, continue to use it for the convos/autos that used it • refuse cleanly to load/restore • try to migrate the key, go through everything and re-encrypt • something else?