Title: ambiguousReceive ### Fault Name `bpel:ambiguousReceive` -- {excerpt} two or more inbound message activities using the same partnerLink and operation but different correlationSets match an incoming request message. {excerpt} ### Description This fault is thrown when two (or more) inbound message activities (i.e. `<[pick](pick.html)>`, `<[receive]>`, etc...) are in a position to consume the same message. This can occur if two (or more) inbound activities using the same partnerLink and operation (but different correlationSets) are activate at the same time and a message arrives that matches more two or more of the activities. In other words, this fault is thrown when there is a race between two activities to consume the same message. The [following section](#examples) provides an example.
ODE does not currently throw this fault. Instead, one of the inbound message activitie will "win" and consume the message.
### {anchor:examples} Examples The following BPEL (based on the example types in the [WS-BPEL 2.0](ws-bpel-20.html) specification) would generate the fault in the ``, and `` activities as soon as a matching message was received : ... ### See Also `<[pick](pick.html)>`,`<[receive]>`