Technical Failures Sample Clauses

Technical Failures. 26.1. The Company, with all its available resources, will prevent any possible malfunctioning in the site. However, the Company does not guarantee that the site will be free from technical failures glitches, and/or malfunctions during the course of this Agreement. 26.2. The Company reserves the right to cancel the Client’s participation in any of its services if deemed necessary. The Client acknowledges that the Company’s site and trading platform may not be free of errors and delays. 26.3. The Company may cancel, terminate or suspend its services if it is available to provide them due to: • Difficulties from computer viruses or bugs; • Unauthorized intervention; • Any fraudulent activity; • Technical failures beyond either party’s control; or if • Any other cause occurs beyond the Company’s control 26.4. The Client accepts that he/she will not be entitled to any increased payouts, bonuses or benefits cause by any error or malfunction in the Company’s platform. If such event occurs, the Client must immediately inform the Company through the available contact methods. 26.5. The Client agrees that the Company may refuse or cancel any order that deems to be a result of any error or malfunction.
AutoNDA by SimpleDocs
Technical Failures. From and after the Commencement Date, in the event that the Transmission Facilities suffer an unexpected failure, such that the Sharee’s Station must temporarily cease broadcasting or operate at reduced power levels, Sharer shall promptly notify Xxxxxx and use commercially reasonable efforts, consistent with past practices, to repair the Transmission Facilities to return the Sharee’s Station, as quickly as practicable, to operations at its full authorized power subject to any restrictions contained in the Transmission Facilities Lease.
Technical Failures. From and after the Commencement Date, in the event that the Transmission Facilities suffer an unexpected failure, such that the Sharee’s Station must temporarily cease broadcasting or operate at reduced power levels, Sharer sha...
Technical Failures. It is possible that you may face disruptions, including, but not limited to errors, disconnections or interferences in communication in the internet services, software or hardware that you have used to avail our services. Trell is not responsible for such factors in the disruption or interruption in the services and you take full responsibility with complete knowledge for any risk of loss or damages caused due to interruption of services for any such reasons.
Technical Failures. The Camera Operator takes no responsibility for the failure of equipment if operated correctly. Failing/corrupt media, overheating equipment, dropped frames etc. are examples of such failures. Although rare, technical failures do occur and is considered out of the Camera Operator’s control.
Technical Failures. Notwithstanding anything to the contrary in this Agreement, Provider shall use the technology tools that Google provides with respect to restrictions and limitations on the exhibition of Provider Content, and Google shall be responsible for any failures, breaks or flaws of such technology tools.

Related to Technical Failures

  • Epidemic Failure “Epidemic Failure” for any particular Product shall mean a failure resulting from defects in material, workmanship, and manufacturing process, including but not limited to the use of Components with known defects. The Epidemic Failure clause shall be invoked [***]. The failure rate may be calculated [***], as determined by BUYER. Epidemic failures do not supersede the requirements of any expressed or implied warranty defined herein. In the case of an epidemic failure, SUPPLIER’s obligation is to propose an action plan to fix the failure of any affected Product within seventy-two (72) hours of discovery. SUPPLIER shall implement this action plan upon BUYER’s acceptance thereof. If the action plan is not acceptable to BUYER, BUYER can require SUPPLIER to repair or replace, at BUYER’s option, the affected Product. In addition to bearing the costs associated therewith, if requested by BUYER, SUPPLIER shall support and provide at SUPPLIER’s expense a sufficient number of units of the Product to permit the field exchange or “hot swap” of Products at customer sites. The parties agree to make all reasonable efforts to complete the repair or replacement of all affected Products within eight (8) Business Days after written notice of epidemic failure by BUYER to SUPPLIER. SUPPLIER also agrees that BUYER will be supported with accelerated shipments of replacement Product to cover BUYER’s supply requirements. If an Epidemic Failure is caused by (i) a design, including a BUYER-provided test process, as required by the Specifications or (ii) a failure by a Component required by the Specifications, (iii) misuse or damage during transit or damage by a third party at no fault of SUPPLIER, SUPPLIER shall perform the obligations in this Section 10.5 and BUYER shall pay to SUPPLIER the fees mutually agreed upon by the parties in writing. If an Epidemic Failure is caused by any other reason other than as set forth in the immediately preceding sentence, SUPPLIER shall perform the obligations set forth in this Section free of charge. Confidential treatment is being requested for portions of this document. This copy of the document filed as an exhibit omits the confidential information subject to the confidentiality request. Omissions are designated by the symbol [***]. A complete version of this document has been filed separately with the Securities and Exchange Commission.

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

  • Epidemic Failure Warranty Supplier warrants all Products against Epidemic Failure for a period of three years after DXC’s Acceptance. Epidemic Failure means the occurrence of the same failure, defect, or non-conformity with an Order in 2% or more of Products within any three-month period.

  • Power Failure Power Failure means the failure of power or other utility service if the failure takes place off the "residence premises". But if the failure results in a loss, from a Peril Insured Against on the "residence premises", we will pay for the loss caused by that peril.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Critical Illness Three (3) days per year, with pay, shall be granted in the case of a critical illness or accident to a member of the employee's immediate family as defined in Section 9.4.2. A statement by the physician verifying the need for the employee to be present with the immediate family member shall be attached to the absence form.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.

  • Pandemic An epidemic that spreads over a wide area, crossing borders and defined as a pandemic by the World Health Organisation (WHO) and/or by the competent local authorities of the country where the loss occurred. Isolation of the person, in the event of suspected illness or proven illness, decided by a competent local authority, in order to avoid a risk of spreading said illness in the context of an epidemic or pandemic.

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