Resolving problems when migrating or importing message flows

Use the advice given here to help you to resolve common problems that can occur when you import or migrate message flows.

Message flows that refer to a migrated user-defined node have connection errors

Scenario: After migration, all message flows that refer to a migrated user-defined node have errors indicating that connections cannot be made.
Explanation: One possible cause is that the original user-defined node had space characters as part of one or more terminal names.
The spaces are wrongly rendered as 'X20'.
Solution:
Edit the user-defined node .msgnode file, which is available in the same project as the flows that you have migrated. Correct any terminal names that are at fault. Ensure that the names are exactly as the message flow node implementation expects.

Scenario: After migration, message flows cannot locate a user-defined node.
Explanation: One possible cause is that the flows do not have the correct reference internally to a user-defined node.
Solution: Select the Locate subflow menu for the node that cannot be located. Using the Browse dialog box, locate the user-defined node (which is in the same project as migrated flows).
The message flow now links to the user-defined node correctly and the task list entry is removed when you save the flow.