Severe Problem Sample Clauses

Severe Problem. Any error, bug, or malfunction that causes the Inktomi Search Engine to become inaccessible to Customer and its Site end users, or that causes any feature of the Inktomi Search Engine to become continuously unavailable.
Severe Problem. A Problem that persists for a period of [*] or more during Peak Hours and [*] or more during Non-Peak Hours.
Severe Problem. Any error, bug or malfunction that causes the Ask Jeeves Service to become inaccessible to Customer and its end-users, or that causes any feature of the Service to become continuously unavailable.
Severe Problem. Any error, bug, or malfunction that causes the Powerize Data Engine to become inaccessible to Inktomi and its Site end users, or that causes any feature of the Powerize Data Engine to become continuously unavailable.
Severe Problem. An error, bug, incompatibility or malfunction, which causes a Service not to operate substantially as designed, and/or renders the Results substantially unavailable to or substantially unusable by Yahoo! (and which lasts for [*] or more), including issues which cause more than [*]% of queries to exceed the Critical Threshold. Once a Moderate Problem has been outstanding for more than [*], either party may, using their judgment, upgrade the issue to a Severe Problem. For the purposes of clarity, in the event that an issue with the monitoring infrastructure falsely identifies a problem that does not in truth exist on a large scale, that false positive will not be considered a Severe Problem (though the issue with the monitoring infrastructure should be addressed in its own right).
Severe Problem. An error, bug, incompatibility, malfunction, corruption, data error or other issue which causes a Service and/or Additional Service not to operate substantially as designed, and/or renders the Returned Data substantially unavailable to or substantially unusable by Yahoo! (and which lasts for [*] or more), including issues which cause more than [*]% of Calls in one or more of the America, AsiaPac or EMEA regions to exceed the Critical Threshold; sudden unanticipated changes in core business metric (RPS, coverage, depth, CRR, yield, revenue, etc.); ads not serving or updating for more than [*] PDAs or from any PDAs in the top [*]% of spend; or a significant degradation of performance reported by more than [*] PDAs. For the purposes of clarity, both parties agree that automated systems to detect Severe Problems do not and may not ever exist. Once a Moderate Problem has been outstanding for more than [*], either party may, using their judgment, upgrade the issue to a Severe Problem. For the purposes of clarity, in the event that an issue with the monitoring infrastructure falsely identifies a problem that does not in truth exist on a large scale, that false [*] Indicates that certain information in this exhibit has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to omitted portions. positive will not be considered a Severe Problem (though the issue with the monitoring infrastructure should be addressed in its own right).
Severe Problem. An error, bug, incompatibility or malfunction, which causes the Services not to operate substantially as designed, and/or renders the Results or Conduit Content substantially unavailable to or substantially unusable by End Users. Once a Moderate Problem has been outstanding for more than four hours, either party may, using their judgment, upgrade the issue to a Severe Problem.
Severe Problem. Any error, bug, or malfunction of the e-lingo Service that causes the e-lingo Translation Engine to become inaccessible to Customer and its Site end users, or that causes any feature of the e-lingo Translation Engine to become continuously unavailable.

Related to Severe Problem

  • Year 2000 Problem The Company and its Subsidiaries have reviewed the areas within their business and operations which could be adversely affected by, and have developed or are developing a program to address on a timely basis, the "Year 2000 Problem" (that is, the risk that computer applications used by the Company and its Subsidiaries may be unable to recognize and perform properly date-sensitive functions involving certain dates prior to and any date after December 31, 1999). Based on such review and program, the Company reasonably believes that the "Year 2000 Problem" will not have a Material Adverse Effect.

  • Problems To endeavour to resolve in a fair and just manner any problems, grievances or difficulties which may be encountered while you volunteer with us;

  • SAVINGS/FORCE MAJEURE A Force Majeure occurrence is an event or effect that cannot be reasonably anticipated or controlled and is not due to the negligence or willful misconduct of the affected party. Force Majeure includes, but is not limited to, acts of God, acts of war, acts of public enemies, terrorism, strikes, fires, explosions, actions of the elements, floods, or other similar causes beyond the control of the Contractor or the Commissioner in the performance of the Contract where non- performance, by exercise of reasonable diligence, cannot be prevented. The affected party shall provide the other party with written notice of any Force Majeure occurrence as soon as the delay is known and provide the other party with a written contingency plan to address the Force Majeure occurrence, including, but not limited to, specificity on quantities of materials, tooling, people, and other resources that will need to be redirected to another facility and the process of redirecting them. Furthermore, the affected party shall use its commercially reasonable efforts to resume proper performance within an appropriate period of time. Notwithstanding the foregoing, if the Force Majeure condition continues beyond thirty (30) days, the Parties shall jointly decide on an appropriate course of action that will permit fulfillment of the Parties’ objectives hereunder. The Contractor agrees that in the event of a delay or failure of performance by the Contractor, under the Contract due to a Force Majeure occurrence: a. The Commissioner may purchase from other sources (without recourse to and by the Contractor for the costs and expenses thereof) to replace all or part of the Products which are the subject of the delay, which purchases may be deducted from the Contract quantities without penalty or liability to the State, or b. The Contractor will make commercially reasonable efforts to provide Authorized Users with access to Products first in order to fulfill orders placed before the Force Majeure event occurred. The Commissioner agrees that Authorized Users shall accept allocated performance or deliveries during the occurrence of the Force Majeure event. Neither the Contractor nor the Commissioner shall be liable to the other for any delay in or failure of performance under the Contract due to a Force Majeure occurrence. Any such delay in or failure of performance shall not constitute default or give rise to any liability for damages. The existence of such causes of such delay or failure shall extend the period for performance to such extent as determined by the Contractor and the Commissioner to be necessary to enable complete performance by the Contractor if reasonable diligence is exercised after the cause of delay or failure has been removed. Notwithstanding the above, at the discretion of the Commissioner where the delay or failure will significantly impair the value of the Contract to the State or to Authorized Users, the Commissioner may terminate the Contract or the portion thereof which is subject to delays, and thereby discharge any unexecuted portion of the Contract or the relative part thereof. In addition, the Commissioner reserves the right, in his/her sole discretion, to make an equitable adjustment in the Contract terms and/or pricing should extreme and unforeseen volatility in the marketplace affect pricing or the availability of supply. "Extreme and unforeseen volatility in the marketplace" is defined as market circumstances which meet the following criteria: (i) the volatility is due to causes outside the control of Contractor; (ii) the volatility affects the marketplace or industry, not just the particular Contract source of supply; (iii) the effect on pricing or availability of supply is substantial; and (iv) the volatility so affects Contractor's performance that continued performance of the Contract would result in a substantial loss. Failure of the Contractor to agree to any adjustment shall be a dispute under the Disputes clause; provided however, that nothing in this clause shall excuse the Contractor from performing in accordance with the Contract as changed.

  • Grievability Denial of a petition for reinstatement is grievable. The grievance may not be based on information other than that shared with the Employer at the time of the petition for reinstatement.

  • Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event. 16.2 A party that becomes aware of a Force Majeure Event which gives rise to, or which is likely to give rise to, any failure or delay in that party performing any obligation under this Agreement, must: (a) promptly notify the other; and (b) inform the other of the period for which it is estimated that such failure or delay will continue. 16.3 A party whose performance of its obligations under this Agreement is affected by a Force Majeure Event must take reasonable steps to mitigate the effects of the Force Majeure Event.