Potentially dumb question - locally, when I run a job, it'll run again as soon as the first one is finished (either successfully or unsuccessfully). This behavior only occurs locally, and not in our staging or prod environments. It's not the end of the world, but is this some setting or configuration that I'm missing which controls this?

This is very unexpected behavior. Is it possible you somehow have two Dagster backends running at the same time?