Troubleshoot

Below gives a few issues that need resolving. They are mostly minor ones but can be annoying. Fixes to be expected shortly.

In case the App displays an error when you set up the examples as in the above, look out for fields for which not a single value is specified. This might still be ok, but those fields will not land in the generated json configuration (see screen to the right in the CREATE screen), in which case the validation detects this and does not persist the definition. Thus just click on the + sign for the specific field. This might be enough or you might need to add a value (which you can then delete again), just ensure that the key occurs in the resulting json (e.g even if it is an empty list or similar).
Sometimes when selecting different job types / templates, the form might not reload properly. This should is alleviated by also selecting a template (‘None’ in case none exists or you need an empty form). In doubt you can still reload the page (should not be necessary) and just select the job type / template combination you need.
Some fields in the job / task definitions might loose focus after typing. This should only be subset of fields, but then pasting into the field helps or you gotta click again to gain focus to continue typing. (fixed in main branch, will be fixed from version v0.2.3)

BACKEND

In case of jobs that are currently not marked as processed but were in progress and thus have single batches in the in-progress state (in the storage), this can prohibit actually open ones to be picked. Likely due to number of in-progress states taken as decision criterion whether to pull new tasks in, in this case without checking that those actually do not run at this point but are state from where the job was stopped. Clearing this in-progress files (that would be cleared next time the job is started anyways) helps in those cases. Fix coming. (fixed in from version v0.2.3 )
If the number of tasks allowed to be in progress at any given time is lower than the number of tasks that can be claimed, the task status of those claimed but not yet in progress will be reset, since the other nodes do not see any status updated. Needs adding of status updates also for the tasks that are not yet processed but in status QUEUED. (fixed in main branch, will be fixed from version v0.2.4)