Describe the problem/error/question
Schedule Trigger is not working correctly. The workflow executed at 19:30 and shows “Jun 4, 19:30:00 Succeeded in 30ms | ID#682” but this timing/result is incorrect. Timezone is correct.
Issue: Workflow should take several minutes to complete (involves Google Sheets → API calls → Claude API → data processing → final Google Sheets update), but shows “Succeeded in 30ms” suggesting it didn’t execute the full workflow.
What is the error message (if any)?
No explicit error message - workflow shows as “Succeeded in 30ms” but the execution timing/behavior is incorrect. Expected execution time: 2-5 minutes for full workflow completion.
Please share your workflow
Schedule Trigger Configuration:
- Cron Expression:
0 30 19 * * *(should trigger at 19:30 daily) - Node ID:
a591f81a-f17f-4a13-ad75-afff2d2dce02
PinData shows execution details:
{
"timestamp": "2025-06-04T19:00:00.012+08:00",
"Readable time": "7:00:00 pm",
"Timezone": "Asia/Singapore (UTC+08:00)"
}
Workflow Structure (trimmed for brevity):
Full workflow includes: 25+ nodes with Google Sheets → data filtering → API calls to Apify → Claude API → data processing → final Google Sheets update. Expected runtime: 2-5 minutes.
Share the output returned by the last node
Last node: “Add Data” (Google Sheets append operation)
Expected output: Successful data append to Google Sheets with processed lead information
Actual behavior: Workflow shows “Succeeded in 30ms” but should take 2-5 minutes to complete the full data processing pipeline
Issue: The 30ms execution time suggests the workflow didn’t run through all nodes or terminated early, despite showing “Success” status.
Information on your n8n setup
- n8n version: [email protected]
- Database (default: SQLite): n8n Cloud (managed)
- n8n EXECUTIONS_PROCESS setting (default: own, main): main (default)
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
- Operating system: n8n Cloud (Linux infrastructure)
ADDITIONAL INFO FOR SCHEDULE ISSUES:
- Timezone configuration: Asia/Singapore (UTC+08:00) - correctly configured in pinData
- Schedule configuration: Cron expression
0 30 19 * * *(should be 19:30 daily) - Expected vs. actual behavior:
- Should trigger at 19:30
(execution log shows correct time) - Should take 2-5 minutes to complete
(shows 30ms) - Should process multiple API calls and data transformations (likely didn’t execute full workflow)
- Should trigger at 19:30
Main concern: The extremely short execution time (30ms) for a complex workflow that should involve multiple HTTP requests, data processing, and Google Sheets operations.
PS: Did the activate-deactivate thingy as well. Did not work!
here