Get trigger's activation detail
- Print
- PDF
Get trigger's activation detail
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
View details of the results of running a trigger.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| GET | /triggers/{triggerName}/activations/{activationId} |
Request headers
For headers common to all Cloud Functions APIs, see Cloud Functions common headers.
Request path parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
triggerName | String | Required | Trigger name |
activationId | String | Required | Execution result ID |
Request query parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
platform | String | Optional | Platform type
|
Request example
The following is a sample request.
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
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | Description |
|---|---|---|
content.activationId | String | Trigger execution result ID |
content.duration | Integer | Trigger execution time (milliseconds) |
content.start | Integer | - |
content.end | Integer | Trigger execution end time (milliseconds)
|
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 | - |
Response status codes
The following describes the response status codes.
| HTTP status code | Code | Message | Description |
|---|---|---|---|
| 400 | 80000 | INTERNAL_EXCEPTION | Request parameter error |
| 400 | 80502 | TRIGGER_PLATFORM_MISMATCH | Trigger platform parameter error |
| 403 | 80002 | SUB_ACC_NO_PERMISSION | Detailed permission error |
| 404 | 80501 | TRIGGER_NOT_FOUND | Trigger not found |
| 404 | 80517 | TRIGGER_ACTIVATION_NOT_FOUND | Execution history not found |
Response example
The following is a sample response.
{
"content": {
"activationId": "03e16f1eb68c45e5a16f1eb68cd5e551",
"duration": 0,
"end": 0,
"logs": [],
"name": "mytrigger",
"namespace": "kHbJQSZDDh3m",
"response": {
"result": {},
"status": "success",
"success": true
},
"start": 1702924096749,
"subject": "kHbJQSZDDh3m"
}
}
Was this article helpful?