hey folks! Is it possible to get caching at the

WorkAction

level? I have a task which would benefit from using the worker API to parallelize things, but the caching granularity at the task level would be too broad, so currently I'm creating

n

tasks instead.

I don't think so. Afair you can cache the outputs of a whole task or the outputs of a whole artifact transform (of one artifact).

With configuration-cache tasks are paralelizable, maybe it's worth using tasks instead of worker API (Tricky, it only runs them in parallel if the configuration is cached)

If the tasks still use the worker api and don't explicitly wait for the result, they should also be run in parallel even without configuration cache enabled.

it isn't so obvious to run via tasks since new "work items" are discovered during execution. Using tasks I have to limit this to those I know upfront (which is already not trivial)

This is among the plans, but not supported right now.

I see, thanks for the update!