---
schema_version: "1"
id: f96a2af25a8ed71ad5795d6ee4766f74ff1a2224870accbc00e8aeaaac55d8c6
title: Transaction Security Metering
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/enhanced_transaction_security_metering.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.enhanced_transaction_security_metering.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dab753d4cdf57b975e173ac43dbacd3a8be5b6ea023e64443d19908473ea0dcb
description: Transaction Security uses resource metering to help prevent malicious or unintentional monopolization of shared, multi-tenant platform resources. Metering prevents transaction security policy evaluations from using too many resources and adversely affecting your Salesforce org.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Transaction Security Metering

Transaction Security uses resource metering to help prevent malicious or unintentional monopolization of shared, multi-tenant platform resources. Metering prevents transaction security policy evaluations from using too many resources and adversely affecting your Salesforce org.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in both Salesforce Classic (not available in all orgs) and Lightning
            Experience.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong>
              Editions</p>
            <p style="margin-bottom:0;">Requires Salesforce Shield or Salesforce Event Monitoring add-on
              subscriptions.</p>
          </td>

        </tr>
      </tbody>
    </table>

Salesforce meters transaction security policies for uniform resource use. If a policy request can’t be handled within three seconds, a fail-close behavior occurs, and access is blocked. Transaction Security implements metering by limiting policy execution. If the elapsed execution time exceeds three seconds, the user’s request is denied.

Here’s an example of how metering works. Let’s say your org has four LoginEvent policies set up with a notification action. A user triggers every policy. The first three execute within three seconds, but the final policy exceeds the three-second limit. Transaction Security stops processing the policies and fails closed, blocking the user’s login request. Because the policy evaluations didn’t finish, a notification isn’t sent.

## Bypass Metering-Related Blocking

Legitimate long-running processes, such as bulk API calls, can cause transaction security policy requests to take more than the allotted time. In these cases, metering initiates and blocks the user’s action.

If you encounter this situation regularly, you can prevent metering from blocking user actions with the bypassMeteringBlock field on the EventSetting metadata type. If all your transaction security policies specify no action, metering doesn’t block user operations. If metering occurs, policy notifications aren’t sent. Policies with block actions still block when triggered.

#### See Also

- [_Metadata API Developer Guide_: EventSettings\\](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_eventsettings.htm)