You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi All - I have created a series of dagster pipelines, and most were working successfully until I received the failure below for one of my pipelines.
Note - I have resolve the below by reloading the workspace, and running the pipeline again, but figured the information below might be useful for others.
Error from Failed Pipeline:
Error when trying to run Failed Pipeline again:
I have checked the formal documentation to find this sort of error, but have been unable to find anything. Even various searches across the internet have yielded no results.
I've run these pipelines previously, and they have operated successfully - the code has not changed either. One potential thought was it could be related to port blocking of another pipeline that is running at the same time. Although, I have had independent pipelines run at the same time successfully without this issue previously.
Has anyone else encountered this issue before? Any ideas would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi All - I have created a series of dagster pipelines, and most were working successfully until I received the failure below for one of my pipelines.
Note - I have resolve the below by reloading the workspace, and running the pipeline again, but figured the information below might be useful for others.
Error from Failed Pipeline:
Error when trying to run Failed Pipeline again:
I have checked the formal documentation to find this sort of error, but have been unable to find anything. Even various searches across the internet have yielded no results.
I've run these pipelines previously, and they have operated successfully - the code has not changed either. One potential thought was it could be related to port blocking of another pipeline that is running at the same time. Although, I have had independent pipelines run at the same time successfully without this issue previously.
Has anyone else encountered this issue before? Any ideas would be greatly appreciated.
Cheers.
Beta Was this translation helpful? Give feedback.
All reactions