Repository navigation
bug: tasks: new tasks created with outdated template version #19744
Description
...if you launch a new Task after updating the supporting template, the new version of the template isn't automatically used? You need to go to the supporting workspace, and then update/restart.
Seems like the Task UI maybe caching a template version?
Reproducible on 2.25.1
Activity
BrunoQuaresma commentedon Sep 22, 2025
After taking a closer look at the code, I think I’ve found the issue.
To create a task, we need to know whether the template has presets. If it does, we must provide them. On screen load, we fetch the template—including the active template version—so we can display the correct preset options. If the user submits the prompt after the screen has loaded, it will use the version that was loaded at that time, not necessarily the most recent one.
This makes the UI solution a bit tricky, since template versions can change in ways that affect the presets. If we still want to automatically create prompts with the latest version, we’d need to handle three scenarios:
Implementation-wise, we’d need to check—right before submission—whether the loaded version is still the active one. If not, we’d compare presets and:
Given the added complexity, I’m wondering if this is something we want to prioritize right now. What do you think?
mtojek commentedon Sep 23, 2025
@BrunoQuaresma, assuming this is something we agreed to deliver in the sprint, my answer is yes.
fix: force task to be created with latest version (#19923)