# Grok Bot background tasks keep getting interrupted mid-run

**URL:** <https://forum.cursor.com/t/grok-bot-background-tasks-keep-getting-interrupted-mid-run/176282>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [October 26, 2026, 9:13pm UTC](https://forum.cursor.com/t/grok-bot-background-tasks-keep-getting-interrupted-mid-run/176282 "2026-10-26T21:13:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raymond\_Weiss](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/raymond_weiss/32/106802_2.png) [@Raymond\_Weiss](https://forum.cursor.com/u/Raymond_Weiss)\
**Post date:** [October 26, 2026, 9:13pm UTC](https://forum.cursor.com/t/grok-bot-background-tasks-keep-getting-interrupted-mid-run/176282/1 "2026-10-26T21:13:53Z")

</div>

### Where does the bug appear (feature/product)?

Grok Bot

### Describe the Bug

Over the last few days, background work started by my Grok Bot keeps dying partway through with “The background task was interrupted before it finished.” It happens several times a day, including multiple times this afternoon (Oct 26, about 4–5:10 PM ET). It kills long build and test jobs that were running fine. Trying to resume the interrupted task by its id fails, so the work has to be restarted from scratch. I haven’t changed anything on my side that lines up with when this started. I’ve also emailed [support@x.ai](mailto:support@x.ai). Is this a known issue? Is there a fix or workaround?

### Steps to Reproduce

Start a long-running build or test job as a Grok Bot background task; it is interrupted partway with “The background task was interrupted before it finished.” Resuming by task id fails.

### Expected Behavior

Background tasks should run to completion, or be resumable by id after an interruption.

### Operating System

Linux

### Version Information

Grok Bot app; OS: Linux cloud box via Grok Bot app

### Additional Information

Also emailed [support@x.ai](mailto:support@x.ai).

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 27, 2026, 9:17am UTC](https://forum.cursor.com/t/grok-bot-background-tasks-keep-getting-interrupted-mid-run/176282/6 "2026-10-27T09:17:22Z")

</div>

Hi @Raymond_Weiss,

This isn’t caused by anything on your side. Grok Bot background tasks currently get about 50 minutes per run, and a task that hits that limit is reported as “interrupted before it finished”. That’s what is cutting off your long builds and test runs. The team is looking at letting background tasks keep going past it.

Resuming by id won’t get around it, since a resumed task gets a fresh 50-minute window. Resuming can also fail when the bot passes the task id in a shortened form that it then can’t find.

In the meantime, you can ask the bot to:

1. Start long builds detached on its computer (for example with nohup or inside tmux, writing output to a log file), then check that log, instead of waiting on the build inside one background task. We haven’t confirmed this for every setup, so let us know if the build still stops.
2. Split the work into stages that each finish well under 50 minutes, such as separate build and test steps or test shards.
