Prevent duplicate processing with Redis item state tracking

I built this tool because we faced a real, recurring problem: managing hundreds of client projects in a weekly automated loop.

There was a time when a single error in that process could create a complete data mess, forcing us to manually clean and re-run everything. The Item Tracker was our solution.

It proved that something simple, when used correctly, can be a game-changer for maintaining order and reliability in your workflows (at least it was for us).

---

How the System Works: A Story of Order from Chaos

Our main automation, which fetches and summarizes data, is where the heavy lifting happens. But its newfound stability comes from a simple, critical collaboration with the Item Tracker. It's like a two-step handshake that happens for every single project.

Our main workflow starts by getting a long list of active projects. For each project, it first asks the Item Tracker: "Is this one already being worked on?" If the answer is no, the Item Tracker immediately puts a temporary "in-progress" note on the project Once our main workflow successfully completes its task for that project, it tells the Item Tracker to remove the "in-progress" note and set a "completed" note.

This simple process is our safety net. If a task fails, that "in-progress" note will eventually disappear, allowing the system to confidently pick up and re-run only that specific item later. ++This saves us from having to start the entire job over from scratch.++