Workflow Compiler error when binding Active Learning image name to input image filename

Search before asking

• I have searched the Inference issues and found no similar bug report.

Bug

I am running a workflow for blueprint processing where preserving the original file name is important for traceability.

Each blueprint has a unique name / identifier, and when I upload images directly, the filenames are preserved correctly. However, when images are sent to my dataset through the Active Learning / Roboflow Dataset Upload block, Roboflow assigns its own UUID-based name instead. That makes the uploaded samples difficult to track back to the original blueprint source.

I tried to solve this by setting the Image Name field in the Dataset Upload block to use the input image name, but I get the following compiler error:

Workflow Compiler expected node: $inputs.image.name to be present in execution graph, but condition failed to be met. This is most likely the bug. Contact Roboflow team through github issues (https://github.com/roboflow/inference/issues) providing full context of the problem - including workflow definition you use.

In short:
I want the image uploaded by the Dataset Upload / Active Learning block to keep the same name as the original input image, instead of receiving a generated UUID.

Environment

• Inference: 1.0

The issue persists both on the serverless API and on batch processing.

Minimal Reproducible Example

Goal

Preserve the original filename of input images when they are uploaded to a Roboflow dataset through the Roboflow Dataset Upload / Active Learning block in a Workflow.

The dataset contains blueprint images with unique identifiers in their filenames, so preserving the original name is important for traceability.

Workflow

Simplified workflow structure:

Input (InferenceImage)
→ processing blocks
→ Roboflow Dataset Upload (Active Learning)

Attempted configuration

I attempted to set the Image Name field in the Dataset Upload block to: steps.name_extract.name

Additional

No response

Are you willing to submit a PR?

• Yes I'd like to help by submitting a PR!

Start with the Workflow Compiler entry point and the Roboflow Dataset Upload/Active Learning block handling for InferenceImage.name; compare the serverless API and batch execution paths. Reproduce the $inputs.image.name or steps.name_extract.name binding failure, then verify that an uploaded image preserves the original filename without compiler errors.