for tag-based job retries, do they have to be defined within the JobDefinition? or can they be added via the launchpad prior to launching a job which doesn't have the retry tags specified in the JobDefinition?

they can be added through the launchpad - it doesn’t have to be on the job definition specifically. As long as the run created from the job has the tag, it will trigger an alert if the conditions are met

hmm okay that's what I thought. and in Dagster cloud do retries work on branch deployments? I've got a job with

dagster/max_retries: 2

and

dagster/retry_strategy: ALL_STEPS

on a branch deployment and it doesn't seem to be retrying when an op fails in the job

Ah we should clarify that- retries currently aren’t supported on branch deployments

Created issue at: https://github.com/dagster-io/dagster/issues/9949

okay cool, no worries just felt like I was taking crazy pills - that clears things up

sorry about that!