Credit Support Failure Sample Clauses

Credit Support Failure. A Party’s guarantor or other provider of credit support for such Party (a “Credit Support Provider”) with respect to the Party, if any, (i) fails to satisfy, perform or comply with any agreement or obligation to be complied with or performed by it in accordance with the credit support document and such failure continues after any applicable grace or notice period, (ii) makes any representation or warranty that proves to be incorrect or misleading in any material respect when made in connection with such Performance Assurance and/or credit support document, or (iii) repudiates, disclaims, disaffirms or rejects, in whole or part, any obligation under, or challenges the validity of, its Performance Assurance and/or credit support document.
AutoNDA by SimpleDocs
Credit Support Failure. A Party’s guarantor or other provider of credit support for such Party (a “Credit Support Provider”) with respect to the Party, if any, (i) fails to satisfy, perform or comply with any agreement or obligation to be complied with or performed by it in accordance with the credit support document and such failure continues after any applicable grace or notice period, (ii) makes any representation or warranty that proves to be incorrect or misleading in any material respect when made in connection with such Performance Assurance and/or credit support document, or

Related to Credit Support Failure

  • Payment Failure Any Credit Party (i) fails to pay any principal when due under this Agreement or (ii) fails to pay, within three Business Days of when due, any other amount due under this Agreement or any other Credit Document, including payments of interest, fees, reimbursements, and indemnifications;

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

  • Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11: (a) no Party shall be in breach of its obligations pursuant to this Agreement except to the extent that the performance of its obligations was prevented, hindered or delayed due to a Force Majeure Event; (b) every Party shall be entitled to claim relief in relation to a Force Majeure Event in regard to its obligations, including but not limited to those specified under Article 4.5; (c) For avoidance of doubt, neither Party’s obligation to make payments of money due and payable prior to occurrence of Force Majeure events under this Agreement shall be suspended or excused due to the occurrence of a Force Majeure Event in respect of such Party. (d) Provided that no payments shall be made by either Party affected by a Force Majeure Event for the period of such event on account of its inability to perform its obligations due to such Force Majeure Event.

  • Act of God Days Act of God" days beyond the allowance by Michigan Law and the Department of Education regulations will be made up by the students and assistants at the end of the school year or at other times as specified by the calendar. Assistants will only receive compensation for the "Act of God" days allowed. When a scheduled day of schoolwork is delayed, association members shall report as near as possible to their regular starting times. Assistants will receive their full day's pay when the school day is shortened due to weather or mechanical problems.

  • H5 Disruption The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Contract it does not disrupt the operations of the Authority, its employees or any other contractor employed by the Authority.

  • Termination Due To Lack Of Funding Appropriation If, in the judgment of the Director of Accounts and Reports, Department of Administration, sufficient funds are not appropriated to continue the function performed in this agreement and for the payment of the charges hereunder, State may terminate this agreement at the end of its current fiscal year. State agrees to give written notice of termination to contractor at least 30 days prior to the end of its current fiscal year, and shall give such notice for a greater period prior to the end of such fiscal year as may be provided in this contract, except that such notice shall not be required prior to 90 days before the end of such fiscal year. Contractor shall have the right, at the end of such fiscal year, to take possession of any equipment provided State under the contract. State will pay to the contractor all regular contractual payments incurred through the end of such fiscal year, plus contractual charges incidental to the return of any such equipment. Upon termination of the agreement by State, title to any such equipment shall revert to contractor at the end of the State's current fiscal year. The termination of the contract pursuant to this paragraph shall not cause any penalty to be charged to the agency or the contractor.

  • Settlement without Consent if Failure to Reimburse If at any time an indemnified party shall have requested an indemnifying party to reimburse the indemnified party for fees and expenses of counsel, such indemnifying party agrees that it shall be liable for any settlement of the nature contemplated by Section 6(a)(ii) effected without its written consent if (i) such settlement is entered into more than 45 days after receipt by such indemnifying party of the aforesaid request, (ii) such indemnifying party shall have received notice of the terms of such settlement at least 30 days prior to such settlement being entered into and (iii) such indemnifying party shall not have reimbursed such indemnified party in accordance with such request prior to the date of such settlement.

  • Obtain Deficiency If Lender chooses to sell any or all of the Collateral, Lender may obtain a judgment against Grantor for any deficiency remaining on the Indebtedness due to Lender after application of all amounts received from the exercise of the rights provided in this Agreement. Grantor shall be liable for a deficiency even if the transaction described in this subsection is a sale of accounts or chattel paper.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!