List of future execution time
Function
List of future execution time.
Debugging
You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
workspace:scheduledTasks:getFuture
Read
-
-
-
-
URI
POST /v1/{project_id}/schedule-task/future-executions
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Unique ID of a project |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | No | String | User token It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| scheduled_type | No | String | Execution period type. The options are as follows: |
| day_interval | No | Integer | If the period is by day, the task is executed at an interval of x days. |
| week_list | No | String | If the period is by week, the value ranges from 1 to 7. Multiple values are separated by commas (,), for example, 1,2,7. |
| month_list | No | String | If the period is by month, the value ranges from 1 to 12. Multiple values are separated by commas (,), for example, 1,3,12. |
| date_list | No | String | If the period is by month, the value ranges from 1 to 31 and L (indicating the last day of the current month). The values are separated by commas (,), for example, 1,2,28,L. |
| time_zone | No | String | Time zone. |
| scheduled_date | No | String | If the period is specified, the value is a specified date in yyyy-MM-dd. |
| scheduled_time | No | String | Specified execution time. The format is HH:mm:ss. |
| expire_time | No | String | Expiration time. |
Response Parameters
Status code: 200
| Parameter | Type | Description |
|---|---|---|
| future_executions | Array of strings | List of future execution time. |
| time_zone | String | Time zone. |
Status code: 400
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 401
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 403
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 404
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 405
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 500
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 503
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Example Requests
{
"scheduled_type" : "FIXED_TIME",
"day_interval" : 1,
"week_list" : "1,2,7",
"month_list" : "1,3,12",
"date_list" : "1,2,28,L",
"time_zone" : "Asia/Shanghai",
"scheduled_date" : "2022-12-23",
"scheduled_time" : "09:00:00",
"expire_time" : "2022-03-07T10:40:43.858Z"
} Example Responses
Status code: 200
Response to a successful request.
{
"future_executions" : [ "string" ],
"time_zone" : "Asia/Shanghai"
} Status Codes
| Status Code | Description |
|---|---|
| 200 | Response to a successful request. |
| 400 | The request cannot be understood by the server due to malformed syntax. |
| 401 | Authentication failed. |
| 403 | Permissions required. |
| 404 | No resources found. |
| 405 | The request method is not allowed. |
| 500 | An internal service error occurred. For details, see the error code description. |
| 503 | Service unavailable. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot