You can turn off periodic resending entirely by setting a very large repeat interval: e.g.
repeat_interval: 10y
However, when a new alert comes along which is grouped with older alerts, the new notification will include *all* the currently firing alerts in that group.
You can change the alerting rule "expr" to have a condition which stops alerting if it's been active for more than 24 hours, perhaps along the lines of
expr: up == 0 unless up offset 24h == 0
expr: up == 0 unless min_over_time(up[24h] offset 24h) == 0 # any fail between 24 and 48 hours ago mutes the alert
But ISTM that timeseries and alerting are being used in an inappropriate way here. If a failure condition can't be resolved, then it's not actionable. Would it be possible instead to mute the alert at source, e.g. by deleting the argo workflow once you've gathered enough info about the failure and are satisfied that the "failure" is resolved?