Get action's activation detail
- Print
- PDF
Get action'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 execution results of a Cloud Functions action.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| GET | /packages/{packageName}/actions/{actionName}/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 |
|---|---|---|---|
packageName | String | Required | Package name
|
actionName | String | Required | Action 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 -X GET 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/packages/{packageName}/actions/{actionName}/activations/{activationId}?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}'
Response
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | Description |
|---|---|---|
content.activationId | String | Action execution history ID |
content.duration | Integer | Action execution time (milliseconds) |
content.start | Integer | Action execution start time (milliseconds)
|
content.end | Integer | Action execution end time (milliseconds)
|
content.logs | String[] | Action log |
content.name | String | Action name |
content.namespace | String | Namespace of the user |
content.response | Object | Action execution result information |
content.response.result | Object | Action execution result |
content.response.result.payload | String | Main function return value for action execution result |
content.response.status | String | Action status |
content.response.success | Boolean | Whether the action execution was successful |
content.subject | String | Information of user who executed the action |
Response status codes
The following describes the response status codes.
| HTTP status code | Code | Message | Description |
|---|---|---|---|
| 400 | 80000 | INTERNAL_EXCEPTION | Invalid request parameter |
| 400 | 80302 | ACTION_PLATFORM_MISMATCH | Invalid platform parameter |
| 403 | 80002 | SUB_ACC_NO_PERMISSION | Detailed permission error |
| 404 | 80301 | ACTION_NOT_FOUND | Action not found |
| 404 | 80322 | ACTION_ACTIVATION_NOT_FOUND | Execution history not found |
Response example
The following is a sample response.
{
"content": {
"activationId": "***fe30d270d4bc29fe30d270debc2f7",
"duration": 3,
"end": 1713936450102,
"logs": [],
"name": "mypackage/myaction",
"namespace": "***QK06kFG8C",
"response": {
"result": {
"payload": "abc"
},
"status": "success",
"success": true
},
"start": 1713936450099,
"subject": "***QK06kFG8C"
}
}
Was this article helpful?