Should a stream have itself as a Flow Target ?

The current flow target of a workspace just controls what stream is used
when computing the pending accepts and pending delivers in the Pending
Changes view.
The default flow target of a workspace just controls whether you get a
warning message when you deliver (if your current flow target is not
your default flow target, you'll get a warning about trying to deliver
to a non-default target).
The flow targets of a stream are just comments on where that stream is
expected to flow its changes.

So the only way a work item would not have been delivered to a
particular stream would be if:
- Nobody actually delivered the change-sets of that work item to that
stream, or
- After those change-sets were delivered, the current configuration of
the stream was "replaced" with a configuration that did not contain
those change-sets.

Cheers,
Geoff

yzwkzfn wrote:

We have a customer with issue that a work item was not delivered to a
particular stream
and its build. Searching through their project space reveals that
the stream to which
the subject was delivered has itself (plust at least 1 stream where it
wasn't delivered)
as a "Flow Target"

Is it reasonable to believe that the apparent cycle in the flow target
might have caused this
issue ?