Windmill

W

Windmill

Join the community to ask questions about Windmill and get answers from other members.

Join

help

general

changelog

Error with Windmill in Coolify

I've got a fresh instance of Windmill in Coolify. The only other thing managed by Coolify is Supabase, all of which are on the same VPS. I'm trying to connect to Supabase's postgres DB with Coolify, but when I attempt to test the connection, I see this error. Connection did not resolve after 5s or job did not start. Do you have native workers or a worker group listening to the proper tag available?...

Windmill Worker Chromium Installation Failure

Hi guys, wanted to see if anyone else had this issue. I am using the standard docker-compose.yml for chromium workers but get this issue. ExecutionErr: ExitCode: 100, last log lines:...

Tooltip on button

Is there any way to add a tooltip to a button via the app editor? Or on a column's header?

Determining if job is suspended with API

Hi, is there a way to determine if a job is in the suspended state using the Windmill API? I've looked at the frontend code and it seems to use JobService for this, but that is hidden. Is there also a way to determine what the resume/cancel URLs are for a suspended run?

No logs when triggering script with curl

I setup windmill using docker compose as per docs. Then I created a simple app to print input to stdout. When I trigger the script from the UI, I can see logs of the script running from UI. However, it doesn't show any "run" when I trigger it using curl (I get expected result similar to when I trigger from UI). Is this intentional behavior?

Consistently getting error when executing scripts with HTTP triggers

We are using version 1.418.0. We have setup some scripts to run via HTTP triggers If we run the scritps directly everything workds when but we call the HTTP endpoint it is almost always fails with the following error ExecutionErr: error during execution of the script: job process killed because Cancelled...

One time schedule

Hey, I couldn't find any reference to make a one-time schedule via API? I would like to schedule a flow/script to be ran just at a certain time (Preferrably given via a unix timestamp or such)...

chromium tag code doesn't work suddenly.

The following code used to work fine, but at some point it started closing automatically whenever I open a new page. Can anyone help me with this? I'm using the cloud version and using the built-in chromium tags. Here's the code I used to check the behavior
No description

error: Top-level await promise never resolved

I have a script using typescript deno that is querying a MongoDB atlas database. When either of the collection querying methods (.find or .findOne) take too long, windmill throws this error
error: Top-level await promise never resolved
await run();
^
at <anonymous> (file:///tmp/windmill/wk-default-e2b39e03fc37-DlTlU/01938d90-f94d-cd94-9e2a-95a351ab7870/wrapper.ts:29:5)
error: Top-level await promise never resolved
await run();
^
at <anonymous> (file:///tmp/windmill/wk-default-e2b39e03fc37-DlTlU/01938d90-f94d-cd94-9e2a-95a351ab7870/wrapper.ts:29:5)
...

Copy paste text from HTML component in App

We are heavily using the HTML component to render data in apps. Is there a way for users to copy paste the context of this component in a deployed app?

Log anonymous app usage

Hi all - we are sending some statistics to App Insights at the end of our flow. We use WM_EMAIL to log who runs a flow, but this is also filled out for flows triggered by an anonymous run app (aka a user is not logged into Windmill). Is there a way to log if a user is actually logged in, or not? Thanks!

crazy expensive for long time waiting query ?

I am using windmill for some background job but with AI queries, it is mostly waiting but I get charged something a bit insane in windmill Any idea on how to fix this? since it won't be feasible to keep it that way for me....

is there a way to prefill forms? pass data to a form via URL params

use case is as follows, we got a form users get to after filling out their data in multiple steps to send this data (connected through windmill) we need to ask some of that same data the user already filled in (prior steps) the form is embedded in a site using an iframe...

can't make mobile styles work

https://app.windmill.dev/public/thrive-health-holdings/b88e89a044f118ea68466287cc973a09 how can I make it work on mobile? this is the global CSS I've used so far: ``` #app-content {...

Folder Quikstart Quide?

I feel like this is a very common use case: You have a list of scripts in a directory and you want to be able to run them with different schedules. In my case I have a python scripts folder with "requirements.txt" but I can't seem to figure out what the easiest way to deploy this is. Theres so many fancy features but getting something like this up and running just doesnt seem possible? I dont want to edit one script at a time. I'd rather have everything synced to git and then push once in a while. Folder push seems to expect a file??? How do I do this? I feel like what I want to do is not that unique....

InternalError: Sql error: error communicating with database

Heya, I'm facing an issue in scheduled flow runs where the database seems to be unavailable sometimes, which leads to the schedule getting deactivated. Any idea how I can prevent this?
No description

Python pycache

We have quite big internal library, bootime for a worker is around 20sec. anything to improve?

Unable to build docker image

Hello all, I'm trying to build the docker image from the docker file at
windmill/Dockerfile
windmill/Dockerfile
I'm constantly running into dependency build issues. Below is the error: ```error: could not compile idna (lib) due to 1 previous error 36.80 warning: build failed, waiting for other jobs to finish......

Unexpected Const Error

When running a typescript (bun) step I receive this error: 534 | const settled = results error: Unexpected const at input.tsx:534:3...

Question on worker memory usage

We have configured a worker group in our compose file with a hard limit of 1024M. However, we still see successful flow executions with a peek much larger - is this expected behavior? I suspect this is Docker deciding to not kill the process if it exceeds temporarily the memory limit, but that we should not rely on this behavior being predictable & instead scale up our worker limit to be a safe % above the peak we observe. Is that assumption correct or do we miss something in the way this works?
No description
Next