Skip to main content

Understand an empty or partial proposal

Empty or partial results require review of data and active rules. They alone do not prove that no solution exists.

Before you start​

Keep the request, period, planning mode and calculation messages. Distinguish mandatory constraints from preferences.

Steps​

  1. Check request dates, skills, quantity and destination.
  2. For an expected candidate, check active status, planning inclusion, qualifications, absences and commitments.
  3. Check availability when required by the mode. The mode without declarations does not disable constraints.
  4. Correct confirmed errors, regenerate and compare covered hours and remaining segments before applying.

Example and expected result​

Fictional example: a favorite has A but the request requires B. Increasing preference does not grant B. If only request A is covered out of two equal requests, coverage remains 50%.

If something goes wrong​

Do not turn a mandatory rule into an option to obtain 100%. Incomplete addresses or unavailable travel calculation can limit results. If data changed after a proposal, generate again before applying.

Continue​