I was able to reproduce similar behavior locally. It looks like the SSH Connector may still be referencing the previous temporary key file generated by the Secrets Retriever after the workflow is reset and executed again.
I’m checking internally with the development team, and I’ll update this thread as soon as I have more information.
We have opened an internal ticket (AP-25765) to resolve this issue. In the meantime, please use the following workaround:
Workaround: Instead of using the variable button in the Settings tab, map your flow variable directly via the Flow Variables tab. This ensures the configuration is correctly saved and persists through workflow reloads.