Failure-Performance of Covenants Sample Clauses

Failure-Performance of Covenants. 3.3.1 In the event the Developer fails to perform in accordance with or to comply with any of the covenants, conditions and agreements which are to be performed or complied with by the Developer in this Agreement (a “Default”) and fails to cure the Default within thirty (30) days (the “Cure Period”) after receiving written notice of the Default or fails to use all Due Diligence in commencing the cure and in proceeding to effectuate the cure. If the Developer is unable to timely cure the default after receiving written notice, the Developer may request an extension of time from the City Commission which may be granted (“Extended Cure Period”) upon presentation of substantial competent evidence establishing the Developer’s good faith and Due Diligence, justifiable reasons for the delay and the amount of time needed to cure the default. In the event that the Developer fails to cure the Default within the Cure Period, or within the Extended Cure Period(s), whichever is greater, such failure will constitute an Event of Default and a fine will be assessed against the owner Developer in the amount of one hundred fifty dollars ($150.00), or such amount as may be set forth in the City Fee Schedule, for each day the Developer remains in Default thereafter.
AutoNDA by SimpleDocs

Related to Failure-Performance of Covenants

  • Performance of Covenants Each covenant or obligation that the Company is required to comply with or to perform at or prior to the Closing shall have been complied with and performed in all material respects.

  • Excuse from performance of obligations If the Affected Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Event, it shall be excused from performance of such of its obligations to the extent it is unable to perform on account of such Force Majeure Event; provided that:

  • Breach of Covenants If the Company breaches any of the covenants set forth in this Section 4, and in addition to any other remedies available to the Buyer pursuant to this Agreement, it will be considered an event of default under Section 3.4 of the Note.

  • Breach of Covenant The Borrower breaches any material covenant or other term or condition of the Subscription Agreement or this Note in any material respect and such breach, if subject to cure, continues for a period of ten (10) business days after written notice to the Borrower from the Holder.

  • Excuse for Nonperformance or Delayed Performance Except with respect to defaults of subcontractors, Contractor/Vendor shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure by Contractor/Vendor to make progress in the prosecution of the work hereunder which endangers such performance) if Contractor/Vendor has notified the Commission or designee within 15 days after the cause of the delay and the failure arises out of causes such as: acts of God; acts of the public enemy; acts of the State and any other governmental entity in its sovereign or contractual capacity; fires; floods; epidemics; quarantine restrictions; strikes or other labor disputes; freight embargoes; or unusually severe weather. If the failure to perform is caused by the failure of a subcontractor to perform or to make progress, and if such failure arises out of causes similar to those set forth above, Contractor/Vendor shall not be deemed to be in default, unless the services to be furnished by the subcontractor were reasonably obtainable from other sources in sufficient time to permit Contractor to meet the contract requirements. Upon request of Contractor, the Commission or designee shall ascertain the facts and extent of such failure, and, if such officer determines that any failure to perform was occasioned by any one or more of the excusable causes, and that, but for the excusable cause, Contractor’s progress and performance would have met the terms of the contract, the delivery schedule shall be revised accordingly, subject to the rights of the State under the clause entitled (in fixed-price contracts, “Termination for Convenience,” in cost-reimbursement contracts, “Termination”). (As used in this Paragraph of this clause, the term “subcontractor” means subcontractor at any tier).

  • Performance of Covenants by Warrant Agent If the Corporation shall fail to perform any of its covenants contained in this Indenture, the Warrant Agent may notify the Registered Warrantholders of such failure on the part of the Corporation and may itself perform any of the covenants capable of being performed by it but, subject to Section 9.2, shall be under no obligation to perform said covenants or to notify the Registered Warrantholders of such performance by it. All sums expended or advanced by the Warrant Agent in so doing shall be repayable as provided in Section 5.3. No such performance, expenditure or advance by the Warrant Agent shall relieve the Corporation of any default hereunder or of its continuing obligations under the covenants herein contained.

  • Termination of Covenants The covenants set forth in this Section 5 shall terminate and be of no further force or effect (i) immediately before the consummation of the IPO, (ii) when the Company first becomes subject to the periodic reporting requirements of Section 12(g) or 15(d) of the Exchange Act, or (iii) upon a Liquidity Event, as such term is defined in the Restated Certificate, whichever event occurs first.

  • Contractor’s Performance Warranties Contractor represents and warrants to the State that:

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Specific Covenants The Borrower fails to perform or observe any term, covenant or agreement contained in any of Section 6.01, 6.02, 6.03, 6.05, 6.10, 6.11 or 6.12 or Article VII; or

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