Home → TEST → Printer Friendly Version
TEST
TEST
1. Gemini Automation
1.1. Itinerary Code Lookup
| Error Type | Error Code | Description of Error |
|---|---|---|
| Gemini Error | G1 | This error occurs because the AI examined the HelpSpot ticket and was unable to find a flight itinerary. In reality, flight information may exist in the ticket, however, it may not be the correct file type or could be formatted in such a way that the AI does not recognize it. |
| G2 | This error occurs whenever the AI successfully identifies a flight itinerary in the HelpSpot ticket, however, for a reason outside of our control it did not extract the flight information in the appropriate format. Please contact IT if you receive this error code. | |
| Interpret Error | I1 | This error occurs whenever the AI only identifies a single flight in the HelpSpot ticket. It may be the case that the employee really only has a single flight (i.e., a one-way trip). However, it could also be the case that the AI just missed some information. |
| I2 | This error occurs whenever the AI extracted flight details, but failed to return values for one or more of the following:
|
|
| I3 | This error occurs whenever the AI failed to extract key flight departure/arrival times, or the times output by the AI were in an unexpected format for reasons outside of our control. The expected time format is: YYYY-MM-DD HH:MM AM/PM. Example: 2025-02-18 11:11 AM |
|
| Insert Error | N1 | This error occurs when one or more airport codes extracted from the flight itinerary by the AI could not be found in the database. For example, airport code "ORD" will match with Chicago O'Hare airport in the database. Meanwhile, the code "ORZ" will not match with any airport in the database; it is not a code used by any known airport. When this occurs, it could be because:
When this occurs, please research the airport code. If it turns out the airport code actually belongs to a valid airport, please reach out to IT so we can add that airport to the database to prevent this from happening again. |
| N2 | This error occurs because after interpreting the information extracted from the flight itinerary, the flight details could not be associated with any show that is currently setup on the CAARs screen. To determine which show a given flight itinerary pertains to, the following logic is used:
When a flight itinerary cannot be matched to a show using the above logic, this error is raised. The cause of this could be because:
|
|
| N3 | This error occurs because the employee/worker a given flight itinerary belongs to could not be found amongst the list of workers assigned to work a given show (setup via CAARs). For example, if "John Doe" had a flight itinerary that was tied to a show in Chicago, but "John Doe" had not been included as one of the workers assigned to work the Chicago show, then this error would occur. This could be because:
|