Review M-Files on G2 & get a $25 gift card Arrow right Review us!

Options
  • State Verified Answer
  • Replies 4 replies
  • Subscribers 11 subscribers
  • Views 181 views
  • Users 0 members are here
Related

Issue with Missing Workflow During Content Replication and Archiving (CRA) from On-Premises to Cloud Vault

Chandani Mourya

Hi everyone,

I'm encountering an issue while performing Content Replication and Archiving (CRA) from an on-premises M-Files vault to a cloud vault. Everything else is replicating fine — object types, class structures, metadata, property definitions, etc., are all copied successfully.

However, there's a specific issue with workflows:

I have two workflows in my on-premises vault. After replication, only one of them appears in the cloud vault. The second workflow is completely missing.

Since cloud vault logs are not available, I created a test vault on the same on-premises server and replicated the data there instead, just to examine the logs.

Here’s what I found:

  • The CRA logs in the test vault indicate that the second workflow is marked as 'deleted' inside unresolved.
  • However, in the original on-premises vault, the missing workflow is clearly present and fully functional, including all states, transitions, and assignments.
  • Importantly, the workflow does not contain any scripts, since scripts are not supported in cloud vaults. So this shouldn’t be causing the issue.

    Workflow (deleted)

I've attached a screenshot of the CRA logs showing the 'deleted' status for the workflow and its states.

I’m unsure why this is happening, and I'm wondering if anyone else has faced a similar issue or found a solution.

Any suggestions, insights, or workarounds are very welcome!

Thank you for your help!

Parents
  • +1

    I did not move anything to cloud vault but I used CRA multiple times...And failed many times on moving workflows. It was generally due 2 things;

    1. There were mentions of user/user groups in conditions/assignments/notifications that does not exist in new vault

    2. There were some pre-post conditions with properties that does not exists or does exist but has different ID's in new vault. So, the condition type does not met.. Like, ID 1234 was "Start Date" and the conditon is "60 days greater or equal from that date" but as the ID's does not match, in the new vault 1234 is a property that is "choose from list". So, the condition type is invalid

    I'd first check those.

Reply
  • +1

    I did not move anything to cloud vault but I used CRA multiple times...And failed many times on moving workflows. It was generally due 2 things;

    1. There were mentions of user/user groups in conditions/assignments/notifications that does not exist in new vault

    2. There were some pre-post conditions with properties that does not exists or does exist but has different ID's in new vault. So, the condition type does not met.. Like, ID 1234 was "Start Date" and the conditon is "60 days greater or equal from that date" but as the ID's does not match, in the new vault 1234 is a property that is "choose from list". So, the condition type is invalid

    I'd first check those.

Children
No Data
M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.