Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se muestra cómo resolver problemas con Cloud Data Fusion.
Cómo recuperar información de errores de una ejecución de canalización fallida
Cuando falla una ejecución de canalización, puedes recuperar información detallada del error.
Cloud Data Fusion 6.11.0 clasifica los errores de canalización por categoría,
motivo y mensaje. Esta clasificación acelera la resolución y reduce la necesidad de examinar registros complejos.
Para obtener detalles del error, sigue estos pasos:
Console
En la Google Cloud consola, abre tu instancia de Cloud Data Fusion
y ve a tu canalización en la página Studio.
En el nodo en el que se produjo el error, haz clic en Ver errores.
Revisa los detalles del error, que incluyen la categoría, el motivo y el mensaje de error.
Opcional: Para descargar registros sin procesar y realizar un análisis más detallado, haz clic en Download raw logs.
Opcional: Para ver los registros sin procesar, haz clic en Ver registros.
La siguiente es una respuesta de ejemplo para un error de complemento:
[
{
"stageName": "Stage Name",
"errorCategory": "Plugin-x",
"errorReason": "Input path gs://x does not exist",
"errorMessage": "Input path gs://x does not exist",
"errorType": "SYSTEM/USER/UNKNOWN",
"dependency": "true/false"
}
]
```
You can also [view advanced logs for your pipelines](/data-fusion/docs/how-to/viewing-stackdriver-logs).
Cómo resolver problemas relacionados con la creación de una instancia de Cloud Data Fusion
Cuando crees una instancia de Cloud Data Fusion, es posible que encuentres el siguiente problema:
Read access to project PROJECT_ID was denied.
Para resolver este problema, inhabilita y vuelve a habilitar la API de Cloud Data Fusion y, luego, crea la instancia.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page provides guidance on resolving issues within Cloud Data Fusion, specifically focusing on retrieving error information for failed pipeline runs and addressing instance creation problems.\u003c/p\u003e\n"],["\u003cp\u003eWhen a pipeline run fails, you can access detailed error information through the Cloud Data Fusion console by navigating to the pipeline in the Studio and clicking "View errors" on the relevant node, which then displays categorized error details.\u003c/p\u003e\n"],["\u003cp\u003eYou can retrieve error details programmatically for failed pipeline runs using a REST API \u003ccode\u003ePOST\u003c/code\u003e request, which categorizes errors into \u003ccode\u003eerrorCategory\u003c/code\u003e, \u003ccode\u003eerrorReason\u003c/code\u003e, and \u003ccode\u003eerrorMessage\u003c/code\u003e properties.\u003c/p\u003e\n"],["\u003cp\u003eIf you encounter a "Read access to project" error when creating a Cloud Data Fusion instance, the solution is to disable and then re-enable the Cloud Data Fusion API before attempting to create the instance again.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Cloud Data Fusion\n\nThis page shows you how to resolve issues with Cloud Data Fusion.\n\nRetrieve error information for a failed pipeline run\n----------------------------------------------------\n\nWhen a pipeline run fails, you can retrieve detailed error information.\nCloud Data Fusion 6.11.0 classifies pipeline errors by category,\nreason, and message. This classification speeds up resolution and reduces the\nneed to examine complex logs.\n\nTo get error details, follow these steps: \n\n### Console\n\n1. In the Google Cloud console, open your Cloud Data Fusion\n instance and go to your pipeline on the **Studio** page.\n\n2. On the node where the error occurred, click **View errors**.\n\n3. Review the error details, which include the error category, error reason,\n and error message.\n\n4. Optional: To download raw logs for further analysis, click\n **Download raw logs**.\n\n5. Optional: To view raw logs, click **View logs**.\n\n### REST\n\nSend a `POST` request to the following endpoint: \n\n curl -H \"Authorization: Bearer $(gcloud auth print-access-token)\"\n -H \"Content-Type: application/json\" \n ${CDAP_ENDPOINT}/v3/namespaces/\u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e/apps/\u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e/workflows/DataPipelineWorkflow/runs/\u003cvar translate=\"no\"\u003eRUN_ID\u003c/var\u003e/classify -X POST\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNAMESPACE_ID\u003c/var\u003e: the ID of the namespace\n- \u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e: the name of the pipeline\n- \u003cvar translate=\"no\"\u003eRUN_ID\u003c/var\u003e: the run ID of the pipeline\n\nThe following is a sample response for a plugin error: \n\n [\n {\n \"stageName\": \"Stage Name\",\n \"errorCategory\": \"Plugin-x\",\n \"errorReason\": \"Input path gs://x does not exist\",\n \"errorMessage\": \"Input path gs://x does not exist\",\n \"errorType\": \"SYSTEM/USER/UNKNOWN\",\n \"dependency\": \"true/false\"\n }\n ]\n ```\n You can also [view advanced logs for your pipelines](/data-fusion/docs/how-to/viewing-stackdriver-logs).\n\nResolve issues with creating Cloud Data Fusion instance\n-------------------------------------------------------\n\nWhen you create a Cloud Data Fusion instance, you might encounter the\nfollowing issue: \n\n Read access to project \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e was denied.\n\nTo resolve this issue, disable and re-enable the\n[Cloud Data Fusion API](/data-fusion/docs/how-to/enable-service), and\nthen create the instance."]]
