Bug Fixing Service Sample Clauses

Bug Fixing Service. For the duration of this Agreement, Odoo SA commits to making all reasonable efforts to remedy any Bug of the Software submitted by the Customer through the appropriate channel (typically, Odoo SA’s service desk email address or website form), and to start handling such Customer submissions within 2 business days. The Customer understands that Bugs caused by a modi1cation or extension that is not part of the oWcial Software will not be covered by this service. As soon as the Bug is 1xed an appropriate remedy will be communicated to the Customer. If the bug has been addressed in a more recent revision of the Covered Version of the Software used by the Customer, the Customer agrees to update its systems to that revision in order to obtain the correction. The Customer will not be asked to upgrade to a more recent Covered Version of the Software as a remedy to a Bug. When a Bug is 1xed in any Covered Version, Odoo SA commits to 1xing the Bug in all more recent Covered Versions of the Software. Both parties acknowledge that as speci1ed in the license of the Software and in the liability section of this Agreement, Odoo SA cannot be held liable for Bugs in the Software.
AutoNDA by SimpleDocs
Bug Fixing Service. ‌ For the duration of this Agreement, Xxxx SA commits to making all reasonable efforts to rem- edy any Bug of the Software and Covered Extra Modules submitted by the Customer through the appropriate channel (typically, the web form or phone numbers listed on xxxx.xxx/xxxx (xxxxx://xxx.xxxx.xxx/help), or when working with an Odoo Partner, the channel provided by the partner), and to start handling such Customer submissions within 2 business days. As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer. If the Customer is using a Covered Version, they will not be asked to upgrade to a more recent Covered Version of the Software as a remedy to a Bug. When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the Bug in all more recent Covered Versions of the Software. Both parties acknowledge that as specified in the license of the Software and in the 7.3 Limitation of Liability section of this Agreement, Odoo SA cannot be held liable for Bugs in the Software or in Covered Extra Modules.
Bug Fixing Service. For the duration of this Agreement, Xxxx SA commits to making all reasonable efforts to remedy any Bug of the Software and Covered Extra Modules submitted by the Customer through the appropriate channel (typically, the web form or phone numbers listed on xxxx.xxx/xxxx (xxxxx://xxx.xxxx.xxx/help), or when working with an Odoo Partner, the channel provided by the partner), and to start handling such Customer submissions within 2 business days. As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer. If the Customer is using a Covered Version, they will not be asked to upgrade to a more recent Covered Version of the Software as a remedy to a Bug. When a Bug is fixed in any Covered Version, Odoo SA commits to fixing the Bug in all more recent Covered Versions of the Software.
Bug Fixing Service. For the duration of this Agreement, ARMS IT commits to making all reasonable efforts to remedy any Bug of the Software or the platform submitted by the Customer through the appropriate channel (typically, the web form or phone numbers listed on armsit.com-Support, and to start handling such Customer submissions within 3 business days.
Bug Fixing Service. During the term of this Agreement, Oxygis agrees to make all reasonable efforts to remedy any bugs in the Software and Covered Add-On Modules submitted by the Client through the appropriate channel (typically the web form or phone numbers listed on xxxxx://xxxxxx.xx/contact-us/, or in the case of collaboration with an Oxygis integrator, the channel provided by the integrator), and to begin processing Client submissions within 2 business days. As soon as the bug is corrected, an appropriate remedy will be communicated to the Customer. If the Customer is using a Covered Version, the Customer will not be required to upgrade to a newer Covered Version of the Software to remedy a bug. When a bug is fixed in a Covered Version, Oxygis agrees to fix the bug in all more recent Covered Versions of the Software. Both parties acknowledge that, as specified in the Software license and in section 7.3 Limitation of Liability of this Agreement, Oxygis is not responsible for bugs in the Software or in the Covered Add-On Modules.
Bug Fixing Service. For the duration of this Agreement, ARMS IT commits to making all reasonable efforts to remedy any Bug of the Software or the platform submitted by the Customer through the appropriate channel (typically, the web form or phone numbers listed on armsit.com-Support, and to start handling such Customer submissions within 3 business days. As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer. Cloud Platform ARMS IT commits to apply the security remedies for any security Bug discovered in a version of the Software hosted on the Cloud Platform, on all systems under its control, as soon as the remedy is available, without requiring any manual action of the Customer.
Bug Fixing Service. For the duration of this Agreement, ReoSuite commits to making all reasonable efforts to remedy any Bug of the Software and Covered Extra Modules submitted by the Customer through the appropriate channel (typically, the phone numbers listed on XxxXxxxx.xxx/#xxxxxxx, or when working with a ReoSuite Partner, the channel provided by the partner), and to start handling such Customer submissions within 2 business days. As soon as the Bug is fixed an appropriate remedy will be communicated to the Customer. Both parties acknowledge that as specified in the license of the Software and in the 7.3 Limitation of Liability section of this Agreement, ReoSuite cannot be held liable for Bugs in the Software.
AutoNDA by SimpleDocs

Related to Bug Fixing Service

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct. Interconnection Service does not necessarily provide the Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on the CAISO Controlled Grid without incurring congestion costs. In the event of transmission constraints on the CAISO Controlled Grid, the Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in the CAISO Tariff in the same manner as all other resources.

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