Hi, I have a job that got interrupted, and the Meltano state db says the job is still running so it won’t start again. I can update the DB myself, but is there perhaps a command or some more elegant way of resolving this? I have looked at the

--force

flag, but from what I understand that only forces a run, but does not finish a job.

I believe the force flag should close out the lock. Also, the lock should be time bound based on a keepalive from the runner, so after a certain amount of time has passed, this in theory would be self-healing. Is this helpful at all and does the above match your experience?

Thanks. I haven’t had time to reproduce the keepalive theory, but it seems the --force flag does not resolve earlier locks. And running again after, without the --force flag, results in the same error saying the pipeline is already running. That being said, it is quite easy to fix this by just running an update. It’s not like this is critical.