The graph can become coherent only through a rebuild that permanently changes retrieval identities.
Duplicate results undermine workflow trust, while an incorrect merge can hide authorized work content.
Who you’d be doing this for
“I pulled the policy twice and got two different answers while my team waited for approval.”
Fang Nishida · Operations Manager
Runs recurring approval and project workflows from content connected to Dash.
What is at stake
Duplicate document identities are producing conflicting answers for active workflow policies. You must weigh a permanent rebuild against the risk of hiding authorized content.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- coherent retrieval vs permission preservation
- cutover speed vs verification depth
- live availability vs reindexing capacity
- graph correctness vs retrieval-side containment
Why Dropbox
Dash connects work content across applications, so duplicate document identities distort the search and answers operations managers depend on.
Written with these in mind
Not your kind of problem? 26 more at Dropbox, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.