Resolving problems when developing message flows

This topic contains advice for dealing with some common problems that can arise when developing message flows:

Migration
Execution
Trace
Appearance
Other

You do not know whether you need to migrate the Version 2.1 IBM primitives

An error message is issued when you save a message flow that contains MQe nodes

Messages are directed to the failure terminal of an MQInput node

Error message BIP2211 is issued by the MQInput node in z/OS

Messages enter the message flow but do not exit

Your execution group is not reading messages from the input queues

The DataFlowEngine terminates while processing messages

Your execution group hangs or terminates with a core dump

You experience problems when sending a message to an HTTP node's URL

QoS1 and QoS2 SCADA messages are not being processed

You cannot determine which node is being referenced in your trace file

You cannot see any alerts when you change user trace

You rename a flow that contains errors, but the task list entries remain

Terminals on a subflow get out of sync as changes are made

The values of your promoted properties are lost after editing

The Message Flow editor experiences problems when opening a message flow and opens in error mode

You get an exception when saving changes to a .tblxmi file

You do not know when to use the MQeMbMsgObject object

Related concepts
Message flows overview