# Title: graphiti-mcp-server Docker container hangs at 100% CPU when processing updates/corrections via add_episode

## TL;DR

[danielchalef (maintainer)]: Closing as #512 has been merged. If this issue impacted you, please pull from main and rebuild your container. Context:
GitHub issue getzep/graphiti#450 (closed, 13 comments): **Description** The graphiti-mcp-server, when run via the provided docker-compose.yml, consistently enters an unresponsive state with 100% CPU utilization after processing an add_episode call that updates or corrects information about a recently added entity.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

Tool: Docker. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Adding completely new, unrelated information seems to work fine, but modifying existing facts reliably triggers the hang. **To Reproduce** Steps to reproduce the behavior: 1. Start the graphiti-mcp-server using docker compose -f mcp_server/docker-compose.yml up -d (using the files from the getzep/graphiti repo). 2. Use the add_episode too