[Bug]: format_task not used

[quertenmont]

Describe the bug

Hello,

I am trying to use the format_task option by defining a flowerconfig.py as follow:

SENSITIVE_KEYS = {"secret", "password"}
REDACTED = "***"


def format_task(task):
    """Redact encryption keys from task kwargs displayed in the Flower UI."""
    kwargs = task.get("kwargs")
    print("debug format_task kwargs:", kwargs)  # Debug print to check kwargs content
    if kwargs and isinstance(kwargs, dict):
        for key in SENSITIVE_KEYS:
            if key in kwargs:
                kwargs[key] = REDACTED

    print("debug format_task redacted kwargs:", kwargs)  # Debug print to check redacted kwargs
    return task

but this seems to have no effect at all, I don't even see the printout when looking at the logs of my flower container.

I am starting flower like this (in case it may have any impact):
celery -A project flower --address=0.0.0.0 --port=5555 --logging=debug --url_prefix=flower
I also tried by adding the --conf argument in the command line (which in principle is not needed, as the flower config is in the current directory). But this has no impact neither

What am I missing ?

Thanks in avdance
Loic

Steps/Code to Reproduce

everything is in the description

Expected Results

I should not see the secrets anymore in the task kwargs of the flower UI.

Actual Results

still see the secrets

[WilliamLindskog]

Hi @quertenmont,

Thanks for opening this. I'll try to take a look at it this week.

[JiwaniZakir]

The title "format_task not used" is actually a self-describing bug — the configuration option is loaded from flowerconfig.py but there's no call site in Flower's view/API layer that actually invokes it when rendering task data. The absence of the debug print output confirms the function is never executed, not just silently failing. You can verify by searching Flower's source for format_task — it likely appears only in config-loading code (e.g., app.py or options.py) but is never retrieved and called in the task detail handlers (e.g., views/tasks.py). The fix would be to find where task kwargs are serialized for the UI response and add a call like task = app.options.format_task(task) there.