# Executions running forever on my local installation (Mac OS) **URL:** \ **Category:** Questions\ **Tags:** executions\ **Created:** [July 18, 2023, 8:55am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255 "2023-07-18T08:55:21Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![n8nonmac](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@n8nonmac](https://community.n8n.io/u/n8nonmac)\ **Post date:** [July 18, 2023, 8:55am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255/1 "2023-07-18T08:55:21Z")
Hi Everyone, I have installed n8n on my Mac through NPM and so far, I’m really enjoying it. I’m running through a few problems but the main one is: Some executions are running for ages, and there’s no way for me to stop them (I restarted the computer, no change, they reappear) - I activated (after I admit) the timeout on workflows - but it doesnt change. ![Screenshot 2023-07-18 at 10.48.43](https://europe1.discourse-cdn.com/n8n/original/3X/1/c/1c4257102f4e90b656f554993dd7c45488c8745e.png) Is there anything I can do to remove those? - **n8n version:** 0.236.2 - **Database (default: SQLite):** default - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** no idea - **Running n8n via (Docker, npm, n8n cloud, desktop app):** npm - **Operating system:** Mac OS Ventura 13.4 ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [July 19, 2023, 6:55am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255/2 "2023-07-19T06:55:59Z")
Hi @n8nonmac, welcome to the community! I am sorry you’re having trouble. Can you check your server logs, to verify whether n8n might have crashed during these executions, preventing a final execution status from being written to the database? And is the workflow possibly using a polling trigger node? These have caused seemingly endless executions to appear in the execution list in the past where the polling action itself failed. I thought this has been fixed though, so it’d be good to understand what exactly is happening in these problematic executions. ---
**Author:** ![n8nonmac](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@n8nonmac](https://community.n8n.io/u/n8nonmac)\ **Post date:** [July 19, 2023, 10:03am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255/3 "2023-07-19T10:03:19Z")
Hi and thanks for reaching out! Do you have any idea what kind of logs and where you would want me to look at (npm on mac) because I’m not sure where are those logs? The workflow uses cron trigger (every 10 minutes) ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [July 19, 2023, 10:07am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255/4 "2023-07-19T10:07:05Z")
So the cron trigger should be fine, but the logs would be interesting. Where exactly these live will depend on how exactly you run your version of n8n and you have it configured. By default, n8n would send logs to the console. So you should see any output directly in the terminal you are launching n8n in. If you are a using a process manager like pm2 you could view using the `pm2 logs` command (or the respective equivalent in other tools of course) If you have `N8N_LOG_OUTPUT=file` and `N8N_LOG_FILE_LOCATION`, the logs would be written into a log file living at the location you have specified. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [October 17, 2023, 10:07am UTC](https://community.n8n.io/t/executions-running-forever-on-my-local-installation-mac-os/28255/5 "2023-10-17T10:07:55Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.