Is there a limit on runs deleted by /api/v1/runs/delete when using filtered metadata

LangSmith Product Help Observability & Evals
1

When using the /api/v1/runs/delete is there a limit of how many runs can be matched when passing metadata.

For example if my metadata is an organization identifier and that matches 1000s of runs, will they all be queued for deletion or does this adhere to a similar limit of 1000 that /api/v1/runs/delete/traces does?

2

Hi @benlammers
Yes, the same limit applies. /api/v1/runs/delete enforces the same 1000-traces-per-request limit whether you delete by trace IDs or by metadata. So if your organization-identifier metadata matches thousands of runs, they won’t all be queued in one call.

Reference: Data purging for compliance

3

Thanks @Steve , follow up question, is there a way to verify which records got queued for deletion, I thought I had queued some for deletion last week but they remain visible in the LangSmith traces dashboard after this weekend.

I recognize they may take longer yet before they are cleaned up but can I verify that a trace is at least queued to be deleted? Does it make sense they are still visible to be queried in LangSmith?

Thanks!