Hello n8n Community,
I’m working on a self-hosted n8n instance (v1.90.2) running in Docker on DigitalOcean. I’m building an analytics workflow that pulls detailed execution data (inputs, outputs, parameters, errors per node) from other workflows for troubleshooting.
The problem I’m facing is that while calls to /api/v1/executions/{id} return HTTP 200 OK with a valid API key, the response body only contains a basic summary of the execution (id, status, timestamps, workflowId, etc.) and does NOT include the expected nodes array with the detailed node-level information. I’m using the n8n API, specifically trying to fetch the full details for individual executions via the /api/v1/executions/{id} endpoint.
I’ve confirmed:
- The API key works correctly for the
/api/v1/executionsendpoint (fetching summary lists). - The same key is used for the
/api/v1/executions/{id}calls. - The API key is set to never expire.
- Checking the container’s environment variables and the
configfile in the persistent volume didn’t reveal settings explicitly limiting execution data detail (N8N_EXECUTION_DATA_SAVE_...variables were not set). - Checking
docker logsduring the API call didn’t show specific errors related to this API request.
It seems the API endpoint itself on my instance version is not returning the full payload with the nodes array, contrary to documentation. This is blocking my ability to build the troubleshooting data processing workflow.
Has anyone encountered this specific behavior in v1.90.2 or other self-hosted versions? Are there any less common configuration options or known issues that could cause the /api/v1/executions/{id} endpoint to return only summaries instead of full details?
Any insights or suggestions on how to diagnose or potentially fix this on my self-hosted instance would be greatly appreciated!
Note: I have also opened an official support ticket, but reaching out to the community as well.