---
title: "Get Trigger's Activation Detail"
slug: "compute-cloudfunctions-v2-gettriggeractivationdetail"
updated: 2026-09-17T10:05:57Z
published: 2026-09-17T10:05:57Z
canonical: "api.ncloud-docs.com/compute-cloudfunctions-v2-gettriggeractivationdetail"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Trigger's Activation Detail

Available in Classic and VPC

Get details of the results of running a trigger.

## Request

This section describes the request format. The method and URI are as follows:

| Method | URI |
| --- | --- |
| GET | /ncf/api/v2/triggers/{triggerName}/activations/{activationId} |

              Note

              

Singapore and Japan Regions are available only in the VPC environment.

### Request headers

For information about the headers common to all Cloud Functions APIs, see [Cloud Functions request headers](/docs/en/compute-cloudfunctions#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94).

### Request path parameters

You can use the following path parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggerName` | String | Required | Trigger name |
| `activationId` | String | Required | Execution result ID |

### Request query parameters

You can use the following query parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `platform` | String | Optional | Platform type - `vpc` (default) \| `classic` |

### Request example

The request example is as follows:

```
curl --location --request GET 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/triggers/trg1-os/activations/e251b49a25094dcd91b49a25093dcdb0?platform=vpc' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Sub Account Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json'
```

## Response

This section describes the response format.

### Response body

The response body includes the following data:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | String | - | Trigger execution details |
| `content.activationId` | String | - | Trigger execution result ID |
| `content.duration` | Integer | - | Trigger execution time (millisecond) |
| `content.start` | Integer | - | Trigger execution start time (millisecond) - Unix timestamp format |
| `content.end` | Integer | - | Trigger execution end time (millisecond) - Unix timestamp format - 0 (fixed value) |
| `content.logs` | String[] | - | Trigger log |
| `content.name` | String | - | Trigger name |
| `content.namespace` | String | - | Namespace of the user |
| `content.response` | Object | - | Trigger execution result information |
| `content.response.result` | Object | - | Trigger execution result |
| `content.response.status` | String | - | Trigger status |
| `content.response.success` | Boolean | - | Whether the trigger execution was successful |
| `content.subject` | String | - | Information of the user that executed the action |

### Response status codes

For information about the HTTP status codes common to all Cloud Functions APIs, see [Cloud Functions response status codes](/docs/en/compute-cloudfunctions#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C).

### Response example

The response example is as follows:

```
{
    "content": {
        "activationId": "03e16f1eb68c45e5a16f1eb68cd5e551",
        "duration": 0,
        "end": 0,
        "logs": [],
        "name": "mytrigger",
        "namespace": "kHbJQSZDDh3m",
        "response": {
            "result": {},
            "status": "success",
            "success": true
        },
        "start": 1702924096749,
        "subject": "kHbJQSZDDh3m"
    }
}
```