Continuation Callout Summary Event Type

Continuation Callout Summary events contain information about all of the asynchronous callouts performed during a transaction, their response status codes, execution times, and URL endpoint destinations. This event type is available in the EventLogFile object in API version 43.0 and later.

For details about event monitoring, see the Trailhead Event Monitoring module or the REST API Developer’s Guide.

  • Type: String
  • Description: A unique ID identifying a sequence of events within a request.
  • Example: SFDC-Continuation-14e3cg85-961d-389e-7bz1-3d171543162a
  • Type: Number
  • Description: Total duration of continuation, in milliseconds.
  • Type: String
  • Description: The type of event. The value is always ContinuationCalloutSummary.
  • Type: Id
  • Description: The 15-character ID of the organization.
  • Example: 00D000000000123
  • Type: Id
  • Description: The ID of the request that initiated a callout.
  • Example: TID:5ILoVKlztX_rDDJcp7
  • Type: String
  • Description: Continuation request form size, in bytes. Depending on how many HTTP requests were used in a continuation, this field can contain up to three space-separated values.
  • Type: String
  • Description: The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID.
  • Example: 3nWgxWbDKWWDIk0FKfF5DV
  • Type: String
  • Description: The size of the callout response, in bytes. Depending on how many HTTP requests were used in a continuation, this field can contain up to three space-separated values.

  • Type: String

  • Description: The HTTP status or internal code returned by the remote endpoint. A status code of 200 indicates that the request was successful. Other status code values indicate the type of problem that was encountered. Depending on how many HTTP requests were used in a continuation, this field can contain up to three space-separated values.

  • Examples:

    • 2000 — The timeout was reached, and the server didn’t get a chance to respond.
    • 2001 — There was a connection failure.
    • 2002 — Exceptions occurred.
    • 2003 — The response hasn’t arrived (which also means that the Apex asynchronous callout framework hasn’t resumed).
    • 2004 — The response size is too large (greater than 1 MB).
  • Type: Boolean
  • Description: Indicates whether the continuation was successful (1) or not (0).
  • Type: String
  • Description: The access time of Salesforce services in GMT.
  • Example: 20130715233322.670
  • Type: DateTime
  • Description: The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). The timezone is GMT.
  • Example: 2015-07-27T11:32:59.555Z
  • Type: String
  • Description: The callout endpoint URL. Depending on how many HTTP requests were used in a continuation, this field can contain up to three space-separated values.
  • Example: http://prod.location.amazonaws.com:1000/orders/order/_search
  • Type: Id
  • Description: The 15-character ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00530000009M943
  • Type: Id
  • Description: The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or the API.
  • Example: 00590000000I1SNIA0
  • Type: String
  • Description: Continuation Visualforce controller size, in bytes. Depending on how many HTTP requests were used in a continuation, this field can contain up to three space-separated values.