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; } } }

Keep active workflows after upgrade?

Kevin Butcher

We're installing TS 6.7.2 on a new server and we're moving over our current backing store. If we also move the workflow store we be able to keep our current active workflows or is it even possible? The concern is that users will have workflows that have not completed and may not be completed until after the upgrade has taken place.

Find more posts tagged with

Comments

vpatel

Workflows are stored in the ContentStore so you should be able to keep them as long as you don't touch your ContentStore. However, it may make sense to submit, version, and edition everything before your migration and as such it may also make sense to end your WFs on your old server. But you could do it either way depending on your situation.

Adam Stoller

We're installing TS 6.7.2 on a new server and we're moving over our current backing store. If we also move the workflow store we be able to keep our current active workflows or is it even possible? The concern is that users will have workflows that have not completed and may not be completed until after the upgrade has taken place.

What platform are you on?
You may need to fix the id-mapping for TS so that users on the new server will be recognized as being who they were on the old server.
You also need to know if the workflows were written correctly to handle timeout situations, since depending on when you do the copy it is possible that one or more workflow might be in the midst of running an externaltask or cgitask operation - so it will either need to timeout and re-initiate the operation or you will have to go through all of the existing jobs on the new server and manually transition tasks that are stuck in limbo.

While this is certainly do-able, I'd recommend trying to get as many old jobs cleaned up before hand as possible.

Also - depending on what the old server was running - are you sure that all the code in the workflows (externaltasks, cgitasks, etc.) will work on the new 672 server as-is? (i.e. this sounds like you are doing an upgrade at the same time as transitioning to a new server)

Kevin Butcher

I've tried just moving the workflow store, but then it dawned on me I would have to move over the underlying files necessary for the workflows to work, filelists, etc.

After considering how difficult this could become I've decided to have all users end their jobs by a particular date.

Like you said. I'm sure it's "doable", but it more work than I'm willing to do when it's actually a good way to get old jobs cleaned up.

Thanks for all your input.