Bugs or errors Clause Samples

The "Bugs or errors" clause defines how software defects, malfunctions, or unintended behaviors are addressed within an agreement. Typically, this clause outlines the responsibilities of the developer or vendor to fix, patch, or otherwise remedy bugs discovered during the use of the software, and may specify timeframes or procedures for reporting and resolving such issues. Its core practical function is to ensure that users have recourse if the software does not perform as intended, thereby allocating responsibility for maintenance and supporting the reliability of the product.
POPULAR SAMPLE Copied 1 times
Bugs or errors. Notwithstanding Microsoft’s Certification, all Software Titles must remain in compliance with all Certification Requirements in the Publisher Guide on a continuing and ongoing basis. Nothing in this Agreement may be construed to relieve Publisher of its obligation to (and Publisher will, as soon as possible after discovery) correct material bugs and errors in Software Titles whenever discovered (including after Commercial Release) in a mutually-agreed manner (which may be via a Title Update). [***]
View SourceView Similar (4)

Related to Bugs or errors

  • Errors State Street shall assume no responsibility for failure to detect any erroneous payment order provided that State Street complies with the payment order instructions as received and State Street complies with the Security Procedure. The Security Procedure is established for the purpose of authenticating payment orders only and not for the detection of errors in payment orders.

  • Correction of Errors Contractor shall perform, at its own cost and expense and without reimbursement from the District, any work necessary to correct errors or omissions which are caused by the Contractor’s failure to comply with the standard of care required herein.

  • No Liability for Errors CenturyLink is not liable for mistakes in their respective signaling networks (including but not limited to signaling links and Signaling Transfer Points (STPs)) and call- related databases (including but not limited to the Line Information Database (LIDB), Toll Free Calling database, local Number Portability database, Advanced Intelligent Network databases, Calling Name database (CNAM), 911/E911 databases, and OS/DA databases).

  • BILLING ERRORS In case of errors or questions about electronic fund transfers from your share and share draft accounts or if you need more information about a transfer on the statement or receipt, telephone us at the following number or send us a written notice to the following address as soon as you can. We must hear from you no later than 60 days after we sent the FIRST statement on which the problem appears. Call us at:

  • Trade Errors The Sub-Advisor will notify the Manager of any Trade Error(s), regardless of materiality, promptly upon the discovery such Trade Error(s) by the Sub-Advisor. Notwithstanding Section 5, the Sub-Advisor shall be liable to the Manager, the Fund or its shareholders for any loss suffered by the Manager or the Fund resulting from Trade Errors due to negligence, misfeasance, or disregard of duties of the Sub Advisor or any of its directors, officers, employees, agents (excluding any broker-dealer selected by the Sub-Advisor), or affiliates. For purposes under this Section 6, “Trade Errors” are defined as errors due to (i) erroneous orders by the Sub-Advisor for the Series that result in the purchase or sale of securities that were not intended to be purchased or sold; (ii) erroneous orders by the Sub-Advisor that result in the purchase or sale of securities for the Series in an unintended amount or price; or (iii) purchases or sales of financial instruments which violate the investment limitations or restrictions disclosed in the Fund’s registration statement and/or imposed by applicable law or regulation (calculated at the Sub-Advisor’s portfolio level), unless otherwise agreed to in writing.