Native scripts will never complete in the default configuration

[strugee]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Install a fresh Nextcloud Flow installation and go through setup
2. Create a "TypeScript (Bun)" script
3. Put //native as the first line and deploy it
4. Try and run your script (this might need to be in a workflow, I haven't had time to fully repro this in a clean environment yet)

Expected behaviour

The script should run

Actual behaviour

The script will be stuck waiting for a worker forever

Server configuration

N/A

Browser

N/A

Additional details

Setting WORKER_TAGS=deno,python3,go,bash,powershell,dependency,flow,other,bun,php,rust,nativets,postgresql,mysql,graphql,snowflake,mssql,bigquery in /etc/environment in the container, then restarting the container, will drain the native queue. This tag list is what you get with the "Reset to all tags" button in the worker configuration screen, described here upstream.

Another solution is to automatically provision native workers.

Kind of disappointing that this really really basic bug slipped though even though Windmill integration was heavily featured at launch and is still being heavily promoted.

[oleksandr-nc]

Thanks for reporting this! You are right - native scripts require at least one worker with the native or nativets tag, which is not included in the default config.

We will look into improving the out-of-the-box experience.

For now, your workaround with WORKER_TAGS is the correct approach, thanks for mentioning it.

[reidellawfirm]

@strugee to be clear, the solution to assigning all tags to the default workers group is to click the 'Reset all tags' button under the 'Edit config' modal?

Were you able to save the reset at all after clicking the reset button? The Windmill/NC Workow Engine is initially setup as Community Edition which seems to prevent any saving of the tags reset button. It is reserved for Enterprise Edition.

So I do not think there is any current option to re-assign the Native tags to the Default workers group unless you have a paid Windmill.dev Enterprise subscription.

[strugee]

@reidellawfirm IIRC I didn't literally use the button, just its documented behavior, specifically because of the Enterprise edition problem you're talking about. You need to set the environment variable on the container host command line in some way.

[reidellawfirm]

@strugee ah understood, thank you. I may have to sign up for EE to test this but its a bummer Windmill/NC Workflow Engine is hobbled by the default setup.