the status of the service itself is: Active: active (exited) and not Active: active (running) Is there a way to ensure it starts if failed, but with the oneshot type as (per my understanding) oneshot causes it to be active but exited

Ahhh ok scratch all that. I was clearly not paying attention and tried to manage the service by using the full path to the service file, rather than the service name.....oops