Skip to content

[Mobile Synthetic Testing] Delete Node Selection Template



POST /api/v1/dialing_task/mobile/templates/{template_uuid}/delete

Overview

Delete a node selection template in the current workspace.

Before You Call and Usage Steps

Only the template snapshot is deleted; synthetic tests, remote nodes, and saved node selections are not deleted. You can still delete the template when the Mobile Synthetic Testing toggle is turned off; you do not need to accept the terms again. The target template must actually exist. The API first performs a get to read the name and then deletes it; it does not idempotently return success while ignoring a non-existent template. Concurrent deletions may return a parameter error.

After a successful deletion, the existing nodeSelection of the test retains the original snapshot, and new processes no longer use this templateUUID. If a timeout occurs, first check whether the template still exists before deciding whether to retry.

Path Parameters

Parameter Name Type Required Description
template_uuid string Y UUID of the template to delete, not a test/node ID.
Example: dsel_example
How to obtain or enter: Obtain the templateUUID from the template list in the current workspace.

Request Headers

Parameter Name Type Required Description
DF-API-KEY string Y OpenAPI authentication credential for the workspace.
Example: <DF-API-KEY>
How to obtain or enter: Obtain an OpenAPI Key with the required permission from API Key Management in the target workspace.

Request Example

curl --request POST 'https://openapi.guance.com/api/v1/dialing_task/mobile/templates/dsel_example/delete' \
  -H 'DF-API-KEY: <DF-API-KEY>'

Response

HTTP 200, application/json. The example below shows the main fields that can be read directly.

Field Type Description
content boolean true if the deletion succeeded.
{
  "code": 200,
  "content": true,
  "errorCode": "",
  "message": "",
  "success": true,
  "traceId": "TRACE-EXAMPLE"
}

Error Response

For authentication, rate limiting, and common request errors, see Common Error Definitions.

HTTP Status errorCode Trigger Condition Message or Response Description Handling
400 ft.ParamsValidateError The identifier, node selection structure/range, name, template count, or protocol parameters do not comply with the current contract Parameter validation failed: {} Correct according to message and the optional content.reason/field, and first retrieve the target again from the list in the current workspace.
409 ft.MobileDialingOperationBusy Timed out while waiting for the workspace mutex; this operation was not executed Another operation is in progress in the current workspace. This operation was not executed. Try again later. When operationExecuted=false/retryable=true, retry after backoff; do not overwrite concurrently.
401 ft.WKSPNotExistOrReleased The workspace no longer exists or has been released after waiting The workspace does not exist or has been released Stop retrying and check that the workspace is valid.
403 ft.WorkspaceIsLocked The workspace is locked after waiting The workspace is locked and cannot be operated on Confirm that the workspace is unlocked and operable.
406 ft.NotFoundWorkspace The workspace does not exist when acquiring the deletion lock The specified workspace was not found Verify that the workspace is valid.
500 ft.InternalServerError An exception occurred while reading storage, formatting historical configuration, or formatting a local static mapping Internal error Narrow the scope to a specific test/template or filter. If it continues to fail, retain the traceId and check the read stage.

Feedback

Is this page helpful?