nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD jobs going away

SethHickel

I have users that love to push file quantities that run jobs for 4 or 5 hours. Recently their jobs have run up against my backup schedule for which I bring down all Autonomy services. Their unfinished job never completes and jobs behind this one to the same server never kick off after we start back up. Is this because they are not time deployments? How do I get OD to remember that it has a queue?

Thanks.

Find more posts tagged with

Comments

Adam Stoller

I have users that love to push file quantities that run jobs for 4 or 5 hours. Recently their jobs have run up against my backup schedule for which I bring down all Autonomy services. Their unfinished job never completes and jobs behind this one to the same server never kick off after we start back up. Is this because they are not time deployments? How do I get OD to remember that it has a queue?

Thanks.

OD doesn't really have a persistent queue - but if you're doing all this through workflows - you can use timeouts in the workflows that allow you to (either manually or programmatically) re-run the task that initiated the deployment and thus complete the job that got interrupted due to the services being taken down.