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.
AutoNDA by SimpleDocs
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. 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. 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. 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.
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).
AutoNDA by SimpleDocs
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.

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 try to resolve fairly any problems, grievances and difficulties you may have while you volunteer with us. • In the event of an unresolved problem, to offer an opportunity to discuss the issues in accordance with the procedures set out in the Volunteer Involvement Policy.

  • 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:

  • 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.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Change in Management Permit a change in the senior management of Borrower.

  • What if a Prohibited Transaction Occurs If a “prohibited transaction”, as defined in Section 4975 of the Internal Revenue Code, occurs, the Xxxxxxxxx Education Savings Account could be disqualified. Rules similar to those that apply to Traditional IRAs will apply.

  • What If I Engage in a Prohibited Transaction If you engage in a “prohibited transaction,” as defined in Section 4975 of the Internal Revenue Code, your account will be disqualified, and the entire balance in your account will be treated as if distributed to you and will be taxable to you as ordinary income. Examples of prohibited transactions are:

  • Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11:

Time is Money Join Law Insider Premium to draft better contracts faster.