Workflow external scripts misisn on nc33

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 33
  • Operating system and version (e.g., Ubuntu 24.04):
    • docker

Summary of the issue you are facing:

On nc33 the Workflow External Scripts does not show up under the list of available options:

It used to work and it is apparently supported on nc33.

There is an open bug logged, though no one seems to be looking at it.

Did any of you would have an idea how to patch it to work?

Thanks!

All the ones in your screenshot are ones that are scoped for usage by normal user accounts. Any chance you’re logged in on an account with admin access but looking at Personal settings ->Flow rather than Admin settings->Flow?

Please post a link to that issue.

Thank you very much, you’re spot on - that was from under “User” settings.

Whilst I didn’t get notification about response, logged in to post update as accidentally loaded “Admin” flow and it popped up there. I’d give a little finger to say that checked that area earlier and it wasn’t there - in the meantime for sure I did restart NC, though it shouldn’t play a role - maybe it was typical PBKAS.

Thanks again!

Here is the link to the issue, which led me to think am not alone: