19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
dagster-de
dagster-cube
gigs-freelance
dagster-wandb
dagster-machine-learning
dagster-bigquery
tools
dagster-dask
dagster-snowflake
dagster-releases
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-dbt
faq-read-me-before-posting
dagster-airbyte
dagster-spatial
dagster-support
announcements
github-discussions
豆瓣酱帮
dagster-feedback
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
Title
g
George Pearse
08/16/2021, 12:55 PMI get this error when I try to re-run from a solid that is used as input to two parallel streams (not sure if that's the cause)
a
alex
08/16/2021, 5:14 PMhmm can you provide some more context? Maybe a video showing how you tried to launch this run?
g
George Pearse
08/17/2021, 5:27 PMIn that case I was trying to run all solids downstream from the last successful solid. Here's another example where I only have the same solid running in parallel, they've all failed, and I'm trying to re-execute them. Does the io_manager store individual inputs to dynamically generated solids? Or should I not expect this to be possible?
I can use re-execute from failure below which is exactly the same request from a pipeline perspective to the above snapshot. The only difference being that the above is a re-execution of a re-execution, whereas the below is the re-execution from failure of a full pipeline. Happy to keep trying to give more detail.
a
alex
08/17/2021, 5:34 PMThe only difference being that the above is a re-execution of a re-execution, whereas the below is the re-execution from failure of a full pipelineThis seems like a good lead
@Dagster Bot issue problems with re-execution of re-execution & dynamic outputs
d
Dagster Bot
08/17/2021, 5:34 PMCreated issue at: https://github.com/dagster-io/dagster/issues/4553
g
George Pearse
08/17/2021, 5:35 PM@alex I'll keep trying to pin it down / consistently reproduce it.