Delete a datasource dataflow

DELETE 
/datasources/:datasource_id/dataflows/:id

Deletes an existing dataflow. The caller (identified by role_id) must have at least owner permission on the datasource (else AUTH-1012). Supports JDBC Bulkload, JDBC Advanced Load, SaaS, Streams, and ArcGIS. Soft vs permanent delete and whether action is used depend on type (see action). Not idempotent for soft delete when the flow is already deleted (SaaS/Streams return GE-1034).

Request

Responses

200

Deletion accepted. Typical messages: "Successfully deleted dataflow" (soft delete or ArcGIS/Advanced sync remove), "Permanently deleted dataflow" (permanent-delete), "Successfully triggered dataflow deletion and is running in background" (JDBC Bulk/Advanced async delete).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Validation or authorization failure. Body is {"Message": " - "}. Common codes: AUTH-1012 (no owner access), IPV-1045 (missing/invalid datasource, dataflow, or Bulk action), GE-1034 (SaaS/Streams invalid action, already deleted, or Streams delete failure), GE-1043 (ArcGIS metadata update in progress), IPV-1002 / IPV-1008 (SaaS flow missing or not owned by datasource).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Backend failure. Body is {"Message": " - "}. Common codes: DTSC-1007 (invalid Advanced/Bulk state, dependent schedule/pipeline/ insights, or delete blocked while DMS is starting), DB-1002 / DB-1003 (DynamoDB update/delete failed), GE-1020 / GE-1021 (persist failures).

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers