Comment 2 for bug 1779093

Sorry, You're right, execution persistence does not affect this action at all.

TripleO UI uses deploy_plan workflow with config_download: true input, that makes the config_download_deploy workflow run as a sub workflow. This results in deploy_plan workflow message to be the last one which updates deployment_status.yaml. tripleoclient currently probably calls these 2 workflows independently.