{"body": "
\n

# Tasks filtering\u00b6

\n

By now, tasks can be filtered by worker, type, state, received and started datetime.\nAlso, filtering by args/kwargs/result/state value available.

\n
\n

## Task filter syntax\u00b6

\n

Flower uses github-style syntax for args/kwargs/result filtering.

\n

> \n
> \n
> - foo find all tasks containing foo in args, kwargs or result
> \n
> - args:foo find all tasks containing foo in arguments
> \n
> - kwargs:foo=bar find all tasks containing foo=bar keyword
> \n
> - result:foo find all tasks containing foo in result
> \n
> - state:FAILURE find all failed tasks
> \n
> \n

\n

If the search term contains spaces it should be enclosed in ” (e.g. args:”hello world”).

\n

For examples, see tests/utils/test_search.py.

\n
\n
\n", "alabaster_version": "0.7.7", "display_toc": true, "title": "Tasks filtering", "sourcename": "tasks_filter.txt", "customsidebar": null, "metatags": "", "current_page_name": "tasks_filter", "next": {"link": "../api/", "title": "API Reference"}, "rellinks": [["api", "API Reference", "N", "next"], ["config", "Configuration", "P", "previous"]], "meta": {}, "parents": [], "sidebars": ["sidebarlogo.html", "localtoc.html", "relations.html", "sourcelink.html", "searchbox.html"], "toc": "

\n
- Tasks filtering
  \n
  - Task filter syntax
  \n
  \n
\n

\n", "prev": {"link": "../config/", "title": "Configuration"}, "page_source_suffix": ".rst"}