Hi ​@ls-avi,

This issue generally occurs when the migration process is not followed.
This KB may be helpful.
 

Hi ​@ls-avi has your issue been resolved? 

Thanks, the issue seems to be resolved. Unfortunately we couldn’t move data because there was only one Nintex content database. But we applied the following steps to the database:

-- 1. Update the WebApplicationId in dbo.Workflows of workflows that are not duplicate:

update dbo.Workflows 
set WebApplicationId = 'CORRECT ID'
where WorkflowId not in (
    -- finds duplicate entries
    select WorkflowId from dbo.Workflows group by WorkflowId having count(*) > 1
) and WebApplicationId = 'INVALID ID';

-- 2. Delete the duplicate entries in dbo.Workflows with an invalid id.
delete from dbo.Workflows where WebApplicationId = 'INVALID ID';

-- 3. Update the WebApplicationId in dbo.PublishedWorkflows of workflows that are not duplicate. Some old versions with an invalid WebApplicationId remain, but that doesn’t seem to matter.

with cte_p1 as (
    -- use distinct values because there are multiple version rows
    select distinct WebApplicationId, WorkflowId from dbo.PublishedWorkflows
), cte_p2 as (
    select * from cte_p1 where WorkflowId not in (
        -- finds duplicate entries
        select WorkflowId from cte_p1 group by WorkflowId having count(*) > 1
    ) and WebApplicationId = 'INVALID ID'
)
update pw set
WebApplicationId = 'CORRECT ID'
from dbo.PublishedWorkflows pw 
    inner join cte_p2 p2 on pw.WorkflowId = p2.WorkflowId and pw.WebApplicationId = p2.WebApplicationId;