Skip to content

Marks the fault as resolved. The Delphix engine will attempt to automatically detect cases where the fault has been resolved; but this is not always possible and may only occur on periodic intervals. In these cases, the user can proactively mark the fault resolved. This does not change the underlying disposition of the fault - if the problem is still present the system may immediately diagnose the same problem again. This should only be used to notify the system of resolution after the underlying problem has been resolved.

Request

Security
ApiKeyAuth
Path
faultIdstring, non-emptyrequired

The ID of the Virtualization Fault.

Bodyapplication/json
ignoreboolean

Flag indicating whether to ignore this fault if it is detected on the same object in the future.

Default:false
resolution_commentsstring

The comments describing the steps taken to resolve a fault.

curl -i -X POST \
  'https://help-api.delphix.com/_mock/data-control-tower/continuous-data/2025.2.0.0/continuous-data-apis-dct-2025.2.0.0/virtualization-fault/{faultId}/resolve' \
  -H 'Authorization: YOUR_API_KEY_HERE' \
  -H 'Content-Type: application/json' \
  -d '{
    "ignore": false,
    "resolution_comments": "string"
  }'

Responses

OK

Bodyapplication/json
jobobject(Job)

An asynchronous task.

Response
{ "job": { "id": "job-123", "status": "RUNNING", "is_waiting_for_telemetry": true, "type": "DB_REFRESH", "localized_type": "DB Refresh", "error_details": "Unable to connect to the engine.", "warning_message": "Failed to remove local MaskingJob, engineId: 3 localMaskingJobId: 7.", "target_id": "vdb-123", "target_name": "vdb", "start_time": "2022-01-02T05:11:24.148Z", "update_time": "2022-01-02T06:11:24.148Z", "trace_id": "string", "engine_ids": [ … ], "tags": [ … ], "engines": [ … ], "account_id": 1, "account_name": "User 1", "percent_complete": 50, "virtualization_tasks": [ … ], "tasks": [ … ], "execution_id": "string", "result_type": "string", "result": {} } }