I’m starting to move our meltano schedules over from legacy elt definitions to jobs. It looks like the

job_name

stored for a job in the

runs

table of the meltano system db is not the “name” of job in meltano.yml, but rather the same format as elt schedules,

env:tap-name-to-target-name

. Is that correct?

Hi, @quinn_batten - yes, that is correct. Internally, what some systemdb tables call 'job name' or 'job id' is what we now refer to as 'state ID'. "Jobs" are now composable workload definitions, and the 'state ID' points to a specific environment's bookmark for a single EL pair.