### Author:  [@rcnijzink](https://renku.discourse.group/u/rcnijzink)
#### Post date: [25 March 2022 15:47 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/3 "2022-03-25T15:47:21Z")
Okay, thank you, that helped! I found now that there seems to be something wrong with cyclic dependencies when I do `renku workflow visualize data/FLEX_results/aus_prec0_2/AdelaideRiver_DS_DalyRoad/Eidt`, I get the error:
```auto
Traceback (most recent call last):
File "/home/rnijzink/.local/bin/renku", line 8, in
sys.exit(cli())
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/cli/exception_handler.py", line 128, in main
result = super().main(*args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/cli/exception_handler.py", line 92, in main
return super().main(*args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/cli/workflow.py", line 1171, in visualize
visualize_graph_command()
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/core/management/command_builder/command.py", line 242, in execute
output = context["click_context"].invoke(self._operation, *args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/home/rnijzink/.local/lib/python3.8/site-packages/inject/ __init__.py", line 342, in injection_wrapper
return sync_func(*args, **kwargs)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/core/commands/workflow.py", line 574, in _visualize_graph
graph = create_activity_graph(activities, with_inputs_outputs=show_files)
File "/home/rnijzink/.local/pipx/venvs/renku/lib/python3.8/site-packages/renku/core/management/workflow/activity.py", line 209, in create_activity_graph
raise ValueError("Cannot find execution order: Project has cyclic dependencies.")
ValueError: Cannot find execution order: Project has cyclic dependencies.
```
But I am sure there are no cyclic dependencies. I inspected the workflow, and the inputs and outputs are fine. Any idea what might cause this?
---
### Author:  [@ralf.grubenmann](https://renku.discourse.group/u/ralf.grubenmann)
#### Post date: [25 March 2022 17:10 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/4 "2022-03-25T17:10:56Z")
I see
> Activity /activities/f2d42bfa0d544ba682c6d47d7716cea2
> Start Time: 2022-03-23T16:35:28+01:00
> End Time: 2022-03-23T16:35:29+01:00
> User: […]
> Renku Version: renku 1.1.1
> Command: python3 src\_py/prep\_flex\_nml.py --inobjectives data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Obj\_cal.txt --inparamfile data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Parameters.txt -ic data/aus\_catch\_chars/AdelaideRiver\_DS\_DalyRoad\_catch\_chars.txt -id data/HYDRO\_input/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/Date.txt -oc work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/config.nml -op work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/param.nml
> Inputs:
> input-1: src\_py/prep\_flex\_nml.py
> inobjectives-2: data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Obj\_cal.txt
> inparamfile-3: data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Parameters.txt
> input-5: data/aus\_catch\_chars/AdelaideRiver\_DS\_DalyRoad\_catch\_chars.txt
> input-7: data/HYDRO\_input/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/Date.txt
> **input-11: work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/param.nml**
> Outputs:
> **output-9: work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/config.nml**
> Parameters:
> i-4: c
> i-6: d
> o-8: c
> o-10: p
> Activity /activities/9574b6e09e2f47aa9c9a69d6fe3e8057
> Start Time: 2022-03-23T16:00:58+01:00
> End Time: 2022-03-23T16:00:59+01:00
> User: […]
> Renku Version: renku 1.1.1
> Command: python3 src\_py/prep\_flex\_nml.py --it 50000 --inobjectives data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Obj\_cal.txt --inparamfile data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Parameters.txt -ic data/aus\_catch\_chars/AdelaideRiver\_DS\_DalyRoad\_catch\_chars.txt -id data/HYDRO\_input/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/Date.txt -oc work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/config.nml -op work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/param.nml
> Inputs:
> input-1: src\_py/prep\_flex\_nml.py
> inobjectives-3: data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Obj\_cal.txt
> inparamfile-4: data/FLEX\_results/aus\_prec1\_0/AdelaideRiver\_DS\_DalyRoad/Parameters.txt
> input-6: data/aus\_catch\_chars/AdelaideRiver\_DS\_DalyRoad\_catch\_chars.txt
> input-8: data/HYDRO\_input/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/Date.txt
> **input-10: work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/config.nml**
> Outputs:
> **output-12: work/FLEX/aus\_prec0\_2/AdelaideRiver\_DS\_DalyRoad/param.nml**
> Parameters:
> it-2: 50000
> i-5: c
> i-7: d
> o-9: c
> o-11: p
emphasis mine. That produces a direct cycle.
Might be that an output was erroneously detected as an input? If the file existed before the execution and wasn’t modified, that would happen.
The commits this happened in are `803bdf997f4efbac38f7d6b4f720e4544e68886a` and `e7f96077ce196d8103f829c738a071aa6c2b5efc`.
As for a fix, deleting those commits might fix things (Do it on a branch first, to see if everything works) and you could rerecord the commands and explicitly specify if something is an input or output with `--input` or `--output` specifically.
I’ve also created [add cycle detection in `renku run` · Issue #2783 · SwissDataScienceCenter/renku-python · GitHub](https://github.com/SwissDataScienceCenter/renku-python/issues/2783) as you should not be able to execute a run that creates a cycle. And the check for that is clearly still there (hence `renku workflow visualize` failing), but somehow it didn’t raise an exception when this workflow was created.
---
### Author:  [@rcnijzink](https://renku.discourse.group/u/rcnijzink)
#### Post date: [28 March 2022 10:00 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/5 "2022-03-28T10:00:04Z")
Oka, thank you!. I did a hard reset to just before those two commits and re-did a couple of things. However, not I have a different error:
```auto
Traceback (most recent call last):
File "[...]/renku/cli/exception_handler.py", line 128, in main
result = super().main(*args, **kwargs)
File "[...]/renku/cli/exception_handler.py", line 92, in main
return super().main(*args, **kwargs)
File "[...]/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "[...]/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "[...]/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "[...]/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "[...]/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "[...]/renku/cli/workflow.py", line 1175, in visualize
text_output, navigation_data = result.output.text_representation(columns=columns, color=not no_color, ascii=ascii)
File "[...]/renku/core/commands/view_model/activity_graph.py", line 214, in text_representation
local_max_y, node_color = self._add_edges_to_canvas(
File "[...]/renku/core/commands/view_model/activity_graph.py", line 149, in _add_edges_to_canvas
if len(colors) < len(EdgeShape.EDGE_COLORS):
AttributeError: type object 'EdgeShape' has no attribute 'EDGE_COLORS'
```
---
### Author:  [@ralf.grubenmann](https://renku.discourse.group/u/ralf.grubenmann)
#### Post date: [28 March 2022 11:13 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/6 "2022-03-28T11:13:54Z")
Thank for letting me know.
I’ve prepared a hotfix that will prevent `renku run`, `renku workflow execute` and `renku workflow iterate` from creating cycles in workflows and as the bug you mentioned above is an easy fix, I’ve included that as well. It’s currently on [chore: release 1.1.4 by Panaetius · Pull Request #2785 · SwissDataScienceCenter/renku-python · GitHub](https://github.com/SwissDataScienceCenter/renku-python/pull/2785) waiting for a review, but you could test that branch already and `visualize` should work as expected.
---
### Author:  [@ralf.grubenmann](https://renku.discourse.group/u/ralf.grubenmann)
#### Post date: [28 March 2022 13:03 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/7 "2022-03-28T13:03:56Z")
It’s been release, so you can upgrade to [renku · PyPI](https://pypi.org/project/renku/1.1.4/)
This version fixes the bug you had above and raises an error if a `renku run` would result in a circular workflow graph.
---
### Author:  [@rcnijzink](https://renku.discourse.group/u/rcnijzink)
#### Post date: [28 March 2022 14:27 UTC](https://renku.discourse.group/t/how-to-find-workflow/581/8 "2022-03-28T14:27:28Z")
Ah super, thank you!