# Agent keeps checking on old tasks **URL:** \ **Category:** Bugs\ **Created:** [April 21, 2026, 4:51pm UTC](https://replit.discourse.group/t/agent-keeps-checking-on-old-tasks/11521 "2026-04-21T16:51:10Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![TravisWilson5](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@TravisWilson5](https://replit.discourse.group/u/TravisWilson5)\ **Post date:** [April 21, 2026, 4:51pm UTC](https://replit.discourse.group/t/agent-keeps-checking-on-old-tasks/11521/1 "2026-04-21T16:51:11Z")
When performing multiple task, agent will be working on a task and then randomly pulling in other tasks, its always the same task #1-6, Then proceed to check and verify the implementation of those task, which they are already done and thus puts the current tasks in waiting. For example - a task it is currently working on - Let me analyze the task: 1. **PM Schedules** (`pm-schedules.tsx`): No location filter at all. Need to add location filter UI + URL param + primaryLocationId defaulting. Also need to check/add backend support. 2. **Fuel Log** (`fuel-log.tsx`): Has location filter but defaults to `" __all__"` instead of primaryLocationId. Need to initialize to primaryLocationId using standard pattern. 3. **Purchase Orders** (`purchase-orders.tsx`): Already uses `locationFilterInitialized` ref + local state - already has the right behavior! Just needs to be refactored to `useFilterParams` pattern. 4. **Requisitions** (`requisitions.tsx`): Same situation as POs - has the behavior but needs the refactoring. what I get back - Let me first check the PM Schedule schema and backend route before implementing: ![image](https://canada1.discourse-cdn.com/flex010/uploads/replit/original/2X/e/e751589926fa3c7748baab9e384741572e047230.png) Then it goes into verifying and working tasks 1-6 which I have explicitly told it to mark complete, have verified the task board that they are marked complete. The headache is that it will add or change a feature we have discussed in later tasks like this Ass Line Button. I later task, and I mean way later tasks I have changed how I want this feature to be and the position of it. Any help on how to get the agent to stop? I wouldn’t care so much if it didn’t cost money. Once for it going rouge and then again for me to have it fix it. ---
**Author:** ![realfunnyeric](https://yyz2.discourse-cdn.com/flex010/user_avatar/replit.discourse.group/realfunnyeric/32/2150_2.png) [@realfunnyeric](https://replit.discourse.group/u/realfunnyeric)\ **Post date:** [April 22, 2026, 8:54pm UTC](https://replit.discourse.group/t/agent-keeps-checking-on-old-tasks/11521/2 "2026-04-22T20:54:30Z")
Best bet is to start a fresh chat to clear the context. Once it pulls in old tasks like that, it usually won’t recover in the same session. ---
**Author:** ![metaphalanx1](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@metaphalanx1](https://replit.discourse.group/u/metaphalanx1)\ **Post date:** [April 24, 2026, 9:16am UTC](https://replit.discourse.group/t/agent-keeps-checking-on-old-tasks/11521/3 "2026-04-24T09:16:39Z")
I have exactly the same issue but it’s with Tasks “1-3” which have been redundant for months now. The problem is it also derails other work, so it’ll get 50% through a series of tasks and then abandon them and start working on Tasks 1-3. It’s super frustrating and reduces confidence. If I start a new chat will it be seamless in terms of picking up where we left off, or might it forget some useful things? ---
**Author:** ![TravisWilson5](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@TravisWilson5](https://replit.discourse.group/u/TravisWilson5)\ **Post date:** [April 25, 2026, 8:31pm UTC](https://replit.discourse.group/t/agent-keeps-checking-on-old-tasks/11521/4 "2026-04-25T20:31:55Z")
I started a new chat and so far it seems to help. I have yet to notice any issue with it not knowing where it left off. Before I started a new chat it had finished a task that was planned and then included the 6 task. Completed task 1234 + session task 1-6. Im not sure if session is a key in finding the bug or not but starting a new chat has seemed to help. Only issue is you wont have the previous chats messages or info.