Question

Migrated LF Environment and changed repository name - now WF Wait events are looking at old repository

Workflow

Updated October 28

asked on March 18, 2019

Hey guys, we just migrated an entire LF environment to a new server over the weekend and are now encountering an issue with Workflow. Any new documents that trigger a workflow work as intended but any existing workflows that had wait conditions are now stuck. I looked at the pending wait conditions in the WF admin console and I can see that the repository listed is the OLD name. How can i update all of these wait conditions with the new repository name? If I do so, and restart the workflow services will the wait conditions be triggered?

Thanks!

1 0

Replies

replied on April 5, 2019

Did you add repository redirects so Workflow knows the repository has been renamed?

0 0

replied on August 11, 2022

Will the redirects apply to the existing "Wait Conditions" when the Repository Name is changed?

I have Redirects for a migrated Repository and Workflow Database for which I changed the Repository Name as it is a DEV Environment. All else works, a scheduled Workflow even ran properly, before being republished. New Workflows Evaluate and Run.

However my Wait Conditions listed with the old Repository Name still do not seem to evaluate even with Redirects.

Thanks

0 0

replied on October 24

Hi there, just wondering if there is a way to manage existing in progress 'Wait Conditions' after the repository server name has changed?

0 0

replied on October 27 • Show version history

1. Please add connection redirects in Workflow Admin Console

2. Add the monitor repository for the new Laserfiche Server in Workflow Configuration Manager Utility

3. Does the repository name get changed? Only the repository server name changed? If the repository name got changed, please update the connection profile and republish the workflow.

1 0

replied on October 28

Thanks Juan that's perfect, really appreciate your help on this

0 0

replied on October 28

It seems to me when I did this for a DEV Copy of a PROD Repository in order to get the "existing" Wait Conditions to Evaluate I had to update the Workflow Database Table with the new Repository Name for those Wait Conditions. I would obviously first open a Support Case to get guidance and direction to confirm if this is supported. The table being "wait_condition_entry". If modifying stop services and perform back ups first. My example was less critical being a DEV mirror of a PROD Build.

0 0

You are not allowed to follow up in this post.

Question

Question

Migrated LF Environment and changed repository name - now WF Wait events are looking at old repository

Replies

Sign in to reply to this post.