Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read-only workflow executions allow code editing in Function node #4018

Closed
ed-parsadanyan opened this issue Sep 4, 2022 · 2 comments · Fixed by #4041
Closed

Read-only workflow executions allow code editing in Function node #4018

ed-parsadanyan opened this issue Sep 4, 2022 · 2 comments · Fixed by #4041

Comments

@ed-parsadanyan
Copy link

Describe the bug
n8n allows to review past executions (either failed or successful). During the review process most of the items are locked due to "read only" mode. However, JS code in the Function is editable.

To Reproduce
Steps to reproduce the behavior:

  1. Create a workflow with a Function Node
  2. Modify workflow settings "Save successful executions" = Save
  3. Run the workflow, then open past execution
  4. Click on the Function node and then the code editor. The code can be changed.

Expected behavior
Code editing is not allowed when viewing past executions

Environment (please complete the following information):

  • OS: Ubuntu Linux 22.04
  • n8n Version 0.193.3
  • Node.js Version NA - docker version
  • Database system postgresql
  • Operation mode main
@Joffcom
Copy link
Member

Joffcom commented Sep 4, 2022

Hey @ed-parsadanyan,

Thanks for reporting this one, does it let you save the edit as well or only edit it while you are looking at it?

@ed-parsadanyan
Copy link
Author

It asks me "Save changes before leaving?", when I press "Yes" and come back again it doesn't seem to save anything.

HOWEVER, new workflows with the same name are created:
image

The workflow with a tag is the original one created yesterday. Several new ones from today were created after I pressed "Save" during the review process of the past execution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants