Google Calendar create-event tool hangs and never finishes, but workflow reports as finished

[mieubrisse]

Describe the problem/error/question

I have an AI agent setup where I send it messages (via Slack) and it calls sub-agents. I asked my agent to schedule two events with this message:

Create me an event tomorrow at 10:45 Eastern at REDACTED for cleaning my Macbook keyboard. And give me a half-hour event right before it for getting to the Apple store.

It responded:

I have created the event for cleaning your Macbook keyboard tomorrow at 10:45 AM Eastern Time at REDACTED, lasting 30 minutes. I also scheduled a half-hour event right before it from 10:15 AM to 10:45 AM for getting to the Apple store. If you need any more help or adjustments, just let me know!

But what I actually have on my calendar are two slightly different events at the same time:

When I open the execution, it seems that the “Create calendar event” tool was called twice successfully with the correct parameters:

There’s no other calendar use in the workflow:

How could it be that two identical events are getting created even though the execution log is saying two correct events were created?

What is the error message (if any)?

No error message.

Please share your workflow

Share the output returned by the last node

The model sends a Slack message telling me it has created two events:

I have created the event for cleaning your Macbook keyboard tomorrow at 10:45 AM Eastern Time at REDACTED, lasting 30 minutes. I also scheduled a half-hour event right before it from 10:15 AM to 10:45 AM for getting to the Apple store. If you need any more help or adjustments, just let me know!

Information on your n8n setup

• n8n version: 1.104.1
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): unset
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on Railway
• Operating system: MacOS

[mieubrisse]

Confirmed that this is happening again. What I sent:

Create 1h event with REDACTED on 14h Sao Paulo time on August 22. Also, add a 30m block beforehand for getting to the appointment

The response:

I have created a 30-minute block on August 22, 2025, from 13:30 to 14:00 Sao Paulo time for getting to the appointment. Additionally, I scheduled a 1-hour event with REDACTED from 14:00 to 15:00 on the same day. If you need any more adjustments or additional events, just let me know!

But what I got on my calendar (same style of duplicated as before):

But the n8n Execution Log is reporting that it created two separate events correctly:

I’m guessing either:

1. The n8n Execution Log has a bug, where it’s not reporting things correctly or
2. The Google Calendar tool node has a bug

[mieubrisse]

I just noticed that in both cases, the second event has a progress spinner and the Execution Log says it’s still running.

From the original request (notice the “runnin for 4h”):

From the second request:

So it seems like the second request is somehow getting listed as “done” (it gets the green checkmark on the graph and the workflow itself completes), but it’s not actually completing.

Now I’m wondering, is this consuming my CPU compute time?