Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hello folks. I feel like I'm missing something pretty basic. I have the following code that runs `CreateRidAlert` task twice and throws warnings:

```
create_alert = CreateAlert()
create_rid_alert = CreateRidAlert()

with Flow('Alert Flow') as flow:
    alert_json = Parameter(name="alert_json", required=True)
    alert = create_alert(alert_json)
    rid_alert = create_rid_alert(alert)
    ifelse(has_rid(alert), rid_alert, None)
    rid = extract_rid(rid_alert)
```

I'd like to remove the `rid_alert = create_rid_alert(alert)` line but then I don't know how to wire up the `ifelse` line with a result to pass to `extract_rid` for data flow. This may not be a clear question.

I'm trying to make a conditional fork in the DAG between alerts with rids and those without

Hi <@UNL3NEYN9>!  The warnings should go away in the latest release of Prefect (0.6.5); however, the double run definitely surprises me.  Any chance you could rewrite the structure of your Flow with some “dummy” print tasks so I can recreate on my machine?

Hmm. This appears to be user error. The warnings claim upstream tasks are run regardless and the viz alludes to that but print statements show otherwise

```
@task
def create_alert(input_param: str) -&gt; str:
    print(f'created alert with param {input_param}')
    return input_param

@task
def always_true(alert: str):
    print('always_true called in ifelse')
    return True

@task
def enrich_alert(alert: str) -&gt; str:
    print(f'enriching_alert {alert}')
    return f'{alert} enriched!'

@task
def post_alert(alert: str) -&gt; None:
    print(f'posting {alert}!')


with Flow('Example flow') as flow:
    input_param = Parameter(name="input_param", required=True)
    alert = create_alert(input_param)
    enriched_alert = enrich_alert(alert)
    ifelse(always_true(alert), enriched_alert, None)
    post_alert(enriched_alert)
state = flow.run(parameters={'input_param': 'test-alert'})
flow.visualize(flow_state=state)
```

so I think I was just thrown by the warning: ```
prefect/tasks/control_flow/conditional.py:89: PrefectWarning: One of the tasks passed to the switch condition has upstream dependencies: &lt;Task: enrich_alert&gt;. Those upstream tasks could run even if the switch condition fails, which might cause unexpected results.
  prefect.utilities.exceptions.PrefectWarning,
```

apologies for wasting your time on a Friday!

Yeah, that warning is from about a year ago when we thought “Airflow-style” branching would be predominant, even though Prefect supports the style of branching you’re doing (which is more like “gating”). We removed it about a week ago :slightly_smiling_face:

No worries at all, we’re glad to hear how you’re approaching Prefect and it helps us adjust it to make it more easy to use!

Yea no worries! Glad you were able to figure it out

Bumped version from `0.6.4` to `0.6.5`. No more warnings! Appreciated