Failed Transactions definition

Failed Transactions is the set of all requests within Total Transaction Attempts that do not return a Success Code within 30 seconds from Microsoft’s receipt of the request.

Failed Transactions is the set of all requests within Total Transaction Attempts that return an Error Code.

Failed Transactions is the set of all requests within Total Transaction Attempts that return an Error Code or otherwise do not return a Success Code within five minutes from 21Vianet’s receipt of the request. "Monthly Uptime Percentage" for API calls within the Stream Analytics Service is calculated as Total Transaction Attempts less Failed Transactions divided by Total Transaction Attempts in a billing month for a given Azure subscription. Monthly Uptime Percentage is represented by the following formula: Monthly Uptime % = (Total Transaction Attempts - Failed Transactions) / Total Transaction Attempts The following Service Credits are applicable to Customer’s use of API calls within the Stream Analytics Service. Monthly Uptime Percentage Service Credit <99.9% 10% <99% 25%

Examples of Failed Transactions in a sentence

• Settlement Failure NettingA Clearing Member may, in the form and manner specified by the Clearing House, request that the Clearing House implement Settlement Failure Netting at an ASP in respect of Failed Transactions (each, a “ Netting Request”).

• The CCP will apply the Fails Management mechanisms with respect to the unsettled Trades following the end of the DVP settlement period of the Intended Settlement Date (Failed Transactions), that is, with respect to the unsettled Settlement Instructions and the sell Trades held at the CCP, as regulated in the following sections and in the supplementing Circulars.

• We explain the details below.Committing, Checkpointing, and Replaying Failed Transactions: On certain write failures, ReiserFS does not crash but continues to commit and checkpoint the failed transaction.

• Consideration of Failed Transactions The sell Trades still held after the end of the designated Release time limit in the CCP on ISD, will be deemed to be Failed Transactions, and they will be governed by the Fails Management mechanisms, including the passing on of costs and the application of the related penalties.

• Ext3 ReiserFS IBM JFS XFSCommitting Failed Transactions Checkpointing Failed TransactionsNot Replaying Failed Checkpoint Writes Not Replaying TransactionsReplaying Failed Transactions Crashing File System×××××××××××××××××× Table 4.10: File System Bugs.

More Definitions of Failed Transactions

Failed Transactions is the set of Indexer Tasks within Total Transaction Attempts that either, a) do not complete within a time period that is 3 times the duration of the input file, or b) do not start processing within 5 minutes of the time that a Media Reserved Unit becomes available for use by the Indexer Task.

Failed Transactions is the set of all requests to the Cognitive Services API within Total Transaction Attempts that return an Error Code. Failed Transaction Attempts do not include API requests that return an Error Code that are continuously repeated within a five-minute window after the first Error Code is received.

Failed Transactions include any API calls included in Total Transaction Attempts that result in either an Error Code or do not return a Success Code.

Failed Transactions means transactions, entered into under the terms of an EquityClear Contract, which have reached ISD but have not yet settled at the ASP.

Failed Transactions is the set of all requests within Total Transaction Attempts that return an Error Code or otherwise do not return a Success Code within five minutes from Microsoft’s receipt of the request. “Monthly Uptime Percentage” for API calls within the Stream Analytics Service is represented by the following formula: 𝑀𝑜𝑛𝑡ℎ𝑙𝑦 𝑈𝑝𝑡𝑖𝑚𝑒 % = 𝑇𝑜𝑡𝑎𝑙 𝑇𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛 𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠 − 𝐹𝑎𝑖𝑙𝑒�� 𝑇𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛𝑠 𝑇𝑜𝑡𝑎𝑙 𝑇𝑟𝑎𝑛𝑠𝑎𝑐𝑡𝑖𝑜𝑛 𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠 Service Credit: Monthly Uptime Percentage Service Credit < 99.9% 10% < 99% 25% Table of Contents / Definitions Stream Analytics – Jobs Additional Definitions: “Deployment Minutes” is the total number of minutes that a given job has been deployed within the Stream Analytics Service during a billing month. “Maximum Available Minutes” is the sum of all Deployment Minutes across all jobs deployed by Customer in a given Microsoft Azure subscription during a billing month. Downtime is the total accumulated Deployment Minutes, across all jobs deployed by Customer in a given Microsoft Azure subscription, during which the job is unavailable. A minute is considered unavailable for a deployed job if the job is neither processing data nor available to process data throughout the minute. Monthly Uptime Percentage for jobs within the Stream Analytics Service is represented by the following formula: Service Credit: Maximum Available Minutes-Downtime Maximum Available Minutes 𝑥 100 Monthly Uptime Percentage Service Credit < 99.9% 10% < 99% 25% Table of Contents / Definitions Traffic Manager Service Additional Definitions: “Deployment Minutes” is the total number of minutes that a given Traffic Manager Profile has been deployed in Microsoft Azure during a billing month.

Failed Transactions are all Valid Key Requests included in Total Transaction Attempts that result in an Error Code or otherwise do not return a Success Code within 30 seconds after receipt by the Content Protection Service.

Failed Transactions means a settlement instruction entered into an ASP, in respect of one or more financial instruments, which has reached ISD, but has not settled at such ASP.