How to prevent LangSmith from tracking update_state()?

[gbaian10]

I asked similar questions in LangChain Discussions, but still don’t know how to solve it.

[hinthornw]

Out of curiosity, why do you want to not track it?

[gbaian10]

Out of curiosity, why do you want to not track it?

Because I got this message on LangSmith

New Pricing:
All free accounts will be rate limited to 5k traces per month starting on July 8th. 

When I'm executing Human-in-the-Loop in LangGraph, I usually need to insert some message and rerun the graph.

Each update_state and each run will generate a trace respectively.

And I think update_state generates very little information.
I don't want to waste my only 5,000 traces on a message that won't help me dev.

---

For example, I just want to confirm whether to continue, so inserting an "ok" produces the result like this.

And I can find this "ok" message in the context of the next rerun.

[gbaian10]

There will be additional charges for each message tracked.

[hwchase17]

The only way to do this is to not have tracing enabled in the environment you are running in. If tracing is enabled, then this will be logged.