Probability of Execution Sample Clauses

Probability of Execution. In specific cases, it may not be possible to execute the order at the desired time; this can occur in the event of significant market volatility, liquidity shortage, or technical failure. The Company shall refrain from executing any order to clients attempting to misuse or manipulate the trading system. The Company shall have the power solely to take any measures it deems appropriate under the said circumstances.
AutoNDA by SimpleDocs

Related to Probability of Execution

  • Applicability of this Agreement This Agreement shall apply to investments made in the territory of one of the Contracting Parties in accordance with its laws and regulations by investors of the other Contracting Party prior to as well as after the entry into force of this Agreement, but shall not apply to any dispute or claim concerning an investment which arose, or which was settled before its entry into force.

  • Contract Renegotiation, Suspension, or Termination Due to Change in Funding If the funds DSHS relied upon to establish this Contract or Program Agreement are withdrawn, reduced or limited, or if additional or modified conditions are placed on such funding, after the effective date of this contract but prior to the normal completion of this Contract or Program Agreement:

  • Possibility of Declining a Request 1. The requested Party shall not be required to obtain or provide information that the applicant Party would not be able to obtain under its own laws for purposes of the administration or enforcement of its own tax laws. The competent authority of the requested Party may decline to assist where the request is not made in conformity with this Agreement.

  • Permissibility of Fees In regard to any other fees, the absence of express authority in this Security Instrument to charge a specific fee to Borrower should not be construed as a prohibition on the charging of such fee. Lender may not charge fees that are expressly prohibited by this Security Instrument or by Applicable Law.

  • No Liability of County’s Personnel All covenants, stipulations, promises, agreements and obligations of the County contained herein shall be deemed to be covenants, stipulations, promises, agreements and obligations of the County and shall be binding upon any member of the County Council or any elected official, officer, agent, servant or employee of the County only in his or her official capacity and not in his or her individual capacity, and no recourse shall be had for the payment of any moneys hereunder against any member of the governing body of the County or any elected official, officer, agent, servants or employee of the County and no recourse shall be had against any member of the County Council or any elected official, officer, agent, servant or employee of the County for the performance of any of the covenants and agreements of the County herein contained or for any claims based thereon except solely in their official capacity.

  • STABILITY OF AGREEMENT Section 1 No amendment, alteration or variation of the terms or provisions of this Agreement shall bind the parties hereto unless made and executed in writing.

  • No Liability for Termination Neither party will be liable to the other for any termination or expiration of this Agreement in accordance with its terms.

  • Independence from Material Breach Determination Except as set forth in Section X.D.1.c, these provisions for payment of Stipulated Penalties shall not affect or otherwise set a standard for OIG’s decision that CHSI has materially breached this CIA, which decision shall be made at OIG’s discretion and shall be governed by the provisions in Section X.D, below.

  • Liability of the Parties 5.1. The Parties shall be liable for non performance or improper performance of their obligations under this Agreement in accordance with the legislation of the Russian Federation.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

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