Viewing & Exporting Results: Interpreting Solve Results
After you initiate the roster generation process in the "Solve" tab, the AI solver will attempt to find a solution that satisfies all your defined rules. The outcome of this process will be indicated by a status message. Understanding these statuses will help you interpret the results and take appropriate action.
If the solver successfully finds a roster that satisfies all your Hard Constraints and attempts to optimize for Soft Constraints, the status will indicate success.
What to do:
An "Infeasible" status means the solver could not find a roster that satisfies all your Hard Constraints simultaneously. This typically occurs when your hard rules contradict each other or when there isn't enough staff or flexibility to meet all mandatory requirements.
What to do:
You need to identify which of your Hard Constraints are causing the conflict. Consider the following:
- Review your Hard Constraints: Look for rules that might be too strict or that might conflict with other mandatory rules.
- Check Staff Availability: Ensure you have enough staff with the necessary availability and qualifications to cover all required shifts according to your rules.
- Consider Promoting to Soft Constraint: If a rule is desirable but not absolutely mandatory, consider changing it from a Hard Constraint to a Soft Constraint (requires a paid subscription). This allows the solver more flexibility.
- Remove or Modify Conflicting Rules: You may need to remove or adjust one or more conflicting Hard Constraints to make the problem solvable.
After making adjustments, return to the "Solve" tab and try generating the schedule again.
An "Error" status indicates that the solver encountered a problem that prevented it from even attempting to find a solution. This is often due to issues with the input data or configuration.
Common Causes and Solutions:
- Staff with Empty Names: Ensure all staff members in the "Staff Details" tab have a name entered.
- Multiple Staff with the Same Name: Each staff member must have a unique name in the "Staff Details" tab.
- No Shift Types Defined: You must define at least one shift type in the "Basic Information" tab.
- No Date Range Set: You must set a start and end date for your roster period in the "Basic Information" tab.
- No Rules Set: You must add at least one rule (constraint or objective) in the "Rules" tab.
- Other Configuration Issues: Review your staff details, shift types, and rules for any other incomplete or unusual configurations.
Address the identified issue(s) and then try generating the schedule again.
If your roster solve process has been running for over an hour and the status is still "pending" or "solving", it's likely that the solve process has timed out. This can happen for a couple of reasons:
- Infeasibility Diagnosis: The solver might be struggling to find a feasible solution due to conflicting or overly strict hard constraints, and the process of diagnosing this infeasibility is taking a long time.
- Problem Complexity: Your roster problem might be genuinely very complex, requiring more than an hour for the solver to find an optimal or feasible solution within the given constraints.
What to do:
After one hour, the solve process has likely been terminated due to a timeout. You can safely delete this solve result. To understand why this has happened and how to potentially resolve it, you are advised to seek help from the developer.
Please contact: [email protected]