Nicolas Crocfer

Closed this issue as we'll continue to use `psycopg2-binary`.

Hi @cin-kevin, Indeed this seems interesting :blush: The main goal of Celery Director is to keep the definitions as simple as possible. If your implementation of this feature doesn't complexify...

This is not linked to the `celery_result_backend` configuration but to the [celery_lock_url](https://github.com/opencve/opencve/blob/fde6e7e1081471b8e2e928cc652ac907a0a7d6ea/opencve/default.cfg#L15) one. With more than 10k users on [OpenCVE.io](https://www.opencve.io/) instance sometimes the Celery chain lasted too long and multiple...

https://github.com/opencve/opencve-docs/pull/14

Thank you for your ideas @sws-lcocco but we'll keep the current behavior for a simple reason: the new version of OpenCVE 2.0 (based on Django) will use the new NVD...

How long did you wait during the freeze? Sometimes the NVD API can take a long time to return the JSON reuslts.

Hi @dppss90008, No this is currenlty not possible, I add it in the backlog.

The v2 branch is still in development and the feature will be available in beta in a few weeks.

Hello @steffiprofileprint , Indeed it can be a new setting to improve the user experience of Celery Director 👍

Unfortunately the feature you're talking about is not yet available in Celery Director. What you want is **dynamic** tasks, but right now Celery Director only support **static workflows** in YAML...