My current build system often fails when a remote network / service behaves badly. 502's, host hangs up, services being down... Today, I have to add custom logic at all of these points as we discover them, or we move to replicating these remotes internally.

• git clone
• go mod download
• docker pull
• apt update
• the list goes on and on...

It would be great if there was retry / expo decay options across the building blocks for these situations. Detecting which are network errors vs which are not could be difficult. Maybe some sort of retry / decay wrapper that could support rerunning an #up after checks defined in CUE (like string processing). Either way, having a consistent and reusable solution would be Grrrreat!