2025-08-18T05:35:31.622367Z WARN openvasd::scheduling: unable to start, removing from queue and set status to failed. Verify that scan using the API *scan_id*=ddfc498e-9318-4aae-a0d2-c899cb27daa2 *e*=Unexpected issue: InvalidResponse(Status { text: “Invalid auto_enable_dependencies value”, code: StringU64(400) })
2025-08-18T05:35:31.622367Z WARN openvasd::scheduling: unable to start, removing from queue and set status to failed. Verify that scan using the API scan_id=ddfc498e-9318-4aae-a0d2-c899cb27daa2 e=Unexpected issue: InvalidResponse(Status { text: “Invalid auto_enable_dependencies value”, code: StringU64(400) })
Yes it is. But you are asking about a very specific detail. And your initial description of
was very misleading because it has nothing to do with the community containers. You are tying to use the HTTP API of openvasd. The response says you are doing something wrong. But without knowing your actual request nobody can tell you what’s wrong .
Only a remark that i’m pretty sure that he doesn’t work on the scanner component and probably has no insights in the question itself so i wouldn’t expect any updates from him.
I would interpret the previous comment more like a more generic hint how to get better / an answer from the community (keep in mind that this is a community driven support forums with Greenbone staff answering on a volunteer basis / as time or knowledge permits).
Edit: IIRC all these new scanner / scanner API features / functionalities are currently also under heavy development, might not work fully / as expected temporarily or could be “underdocumented” so it might be required to wait some more months before things are getting more stable / documented.