Nope, deletion of those jobs is impossible for a reason. When the job is in that status, its tasks are being created by Flamenco Server, and nobody else should be touching the job.

I think it's need to have ability to remove jobs in 'under-construction' status, anyway, even if it will be fixed.

Implemented in ff9624d4f37ab035c27d1d5c59c654f88656ad49 (Blender Cloud add-on) and 5f96d2e50b852dcc1bd350dafc72dea67e02983e (Flamenco Server).

Implemented in 7bbbe3c (auto-delete offline workers) and c52c65d (allow auto-deletion in configurable status)

Committed in 4fe11d99f6a00a7fdb0ff2d4a85eacb37051db84

Yes it helps. Looks like i can launch it now.

Please try [Flamenco Manager 2.4-dev6](flamenco.io/download/flamenco-manager-2.4-dev6-linux.tar.gz). If you go to setup mode (./flamenco-manager -verbose -setup) and re-save your configuration, it should automagically remove the variable-name variable for you.

I can confirm the first issue; there is a regression bug in Flamenco Manager 2.3 that causes this duplicate variable.

There are two things wrong:

It now shows 5 KiB of 'head' and 10 KiB of 'tail', except when accessing the URL with WGet/Curl, in which case it downloads the entire log file. See log_server.go.

I was looking into something like this for the create-video task in the blender-render job compiler for the server. I want to be able to set the ffmpeg arguments that are being used to create the resulting video. As I was digging into this, I thought that using a variable override in the manager, similar to the path override for ffmpeg, could allow for at least making the output file an MP4 vs MKV. Is this barking up the wrong tree?

In e47780a63378e6aa664ba69566323a6396b798eb I changed the Manager so that soft-failed tasks are treated similarly to queued tasks. They are now retried by other workers as you'd expect.

'Normal' is fine, I'll look into it.