Hi - I am trying to debug a flow with a case statement inside apply_map. • Although no errors are being raised, the case statement seems to be running twice with only one mapped task to complete. • The other issue I am seeing is

SKIP signal raised: SKIP('Provided value "True" did not match "False"')

. • In prefect cloud the

case

statement continues to run indefinitely even though the flow has terminated. ## Logs

[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(True)': Starting task run...
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(True)': Finished task run for task with final state: 'Mapped'
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(True)[0]': Starting task run...
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(True)[0]': Finished task run for task with final state: 'Success'
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(False)': Starting task run...
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(False)': Finished task run for task with final state: 'Mapped'
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(False)[0]': Starting task run...
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | SKIP signal raised: SKIP('Provided value "True" did not match "False"')
[2021-02-22 08:49:04-0600] INFO - prefect.TaskRunner | Task 'case(False)[0]': Finished task run for task with final state: 'Skipped'

Any thoughts on what is going on here. Thanks

Hi @itay livni - when you say the task is running indefinitely, do you mean it's taking up resources indefinitely or the UI is not showing it as ending? It's possible this is just the UI not being able to read an ending timestamp for the task run

@nicholas How do you check if it's taking up resources?

I believe most of the behavior here is expected (based on the above logs): 1. the case statement where the case ==

True

maps one task which succeeds 2. the case statement where the case ==

False

maps one run, which then raises a SKIP signal because the case doesn’t match 3. the mapped task that appears to run indefinitely has a log confirming that it ends

@Dylan I dont see an end_time. But maybe you can point me where to look.

So it’s running once, the first time it’s generating all of the mapped runs, which is why it ends in a mapped state

Ok. Any next steps on my part?

@nicholas Do you think this is a UI bug?

Ok. I'll try to put something together. There is some bug. A flow from yesterday still shows the skipped case statement running

Thanks for confirming @itay livni - I'll open a ticket to fix that in the UI