Data Export Tasks do not re-prompt SQL parameters on execution (potentially unsafe behavior)

[DriessenUwe]

Description

Description:
This behavior can easily lead to incorrect exports without user awareness.
I’ve encountered a behavior with Data Export Tasks in DBeaver that seems counterintuitive and potentially error-prone when working with parameterized SQL.

Setup:

A SQL query using parameters (e.g. :year)
A Data Export Task created from that query

Observed behavior:

On the first execution, the parameter is prompted as expected
On subsequent executions, the previously entered value is silently reused
There is no prompt for the parameter
There is no visible way in the task configuration to review or modify the stored parameter value

Expected behavior:
Each execution of the task should prompt for parameter values (similar to running the query in the SQL editor), or at least provide a clear and accessible way to review/edit them before execution.

Why this is problematic:

It is very easy to unintentionally run exports with outdated parameters (e.g. wrong year)
The behavior is inconsistent with how parameterized queries work in the SQL editor
It creates a false sense of safety in recurring reporting tasks

Additional concern:
From a UX perspective, this feels like an incomplete automation:

The task automates execution
But freezes exactly the part that is expected to be dynamic (the parameter)

Questions:

Is this behavior intentional?
Is there a way to force parameter prompts on each task execution?
Are there recommended best practices for recurring exports with changing parameters (without duplicating tasks per parameter value)?

Thanks in advance for clarification.

DBeaver Version

Community Version 26.0.3.202604191653

Operating System

Win 11

Database and driver

No response

Steps to reproduce

No response

Additional context

No response

[davestokes]

@DriessenUwe Thank you for your report.

[E1izabeth]

@DriessenUwe

Here is the setting for that

Does it satisfy your needs?