Priority 3 Errors definition
Examples of Priority 3 Errors in a sentence
RevQ shall use its best efforts to provide a solution for problems designated a Priority 3 Errors within thirty (30) calendar days of receipt of an Error report.
Priority 3 Errors Error that causes less significant Software features to be unavailable or minimal business impact, but Customer’s production use is continuing.
Client shall report any and all Errors, indicating the severity of such Error (as set forth in Paragraph (3) below) within the M*Modal Products (each, an “Error Notice”) to the M*Modal Support Team as follows: For Priority 1 Errors, by both telephone and email, seven (7) days per week, twenty-four (24) hours per day; for Priority 2 and Priority 3 Errors, by both telephone and email during normal M*Modal business days and business hours: Monday — Friday (non-holidays), 9:00 am — 5:00 pm.
For Priority 2 and Priority 3 Errors, any Error Notice received after M*Modal business hours will be deemed to be received by M*Modal on M*Modal’s immediately following business day.
For Priority 2 and Priority 3 Errors, any Error Notice received after M*Modal business hours will be deemed to be received by M*Modal on M*Modal's immediately following business day.
Priority 3 Errors - Simpro shall (i) provide an Initial Response within one (1) Business Day; (ii) initiate Management Escalation within three (3) Business Days; and (iii) provide Customer with a Status Update within three (3) Business Days if Simpro cannot resolve the Error.
Client shall report any and all Errors, prominently indicating the severity of such Error (as set forth in paragraph 3, below) within the M*Modal Products (each, an “Error Notice”) to the M*Modal Support Team as follows: For Priority 1 Errors, by both telephone and email, seven (7) days per week, twenty-four (24) hours per day; for Priority 2 and Priority 3 Errors, by both telephone and email during normal M*Modal business days and business hours: Monday – Friday (non-holidays), 9:00 am – 5:00 pm.
With regard to errors and malfunctions, which from an objective point of view only have a minor impact on the functionalities and availability of the Xovis Flow Service (Priority 3 Errors as specified in section 3.2), Xovis shall be entirely free to at its sole discretion address any such issue in one of the later releases of the software application that is basis to the Xovis Flow Service.
Priority 3 Errors that are non- disabling or cosmetic and clearly have little or no impact on the normal operation of the Services.
M*Modal shall report any and all Errors, prominently indicating the severity of such Error (as set forth in paragraph (3), below) within the M*Modal Products (each, an “Error Notice”) to the Client Contact as follows: For Priority 1 Errors, by both telephone and email, seven (7) days per week, twenty-four (24) hours per day; for Priority 2 and Priority 3 Errors, by both telephone and email during normal M*Modal business days and business hours: Monday - Friday (non-holidays), 9:00 am - 5:00 pm.