The shard rebalance protects future capacity while exposing conflicting versions of live designs.
Write availability during the migration is pulling against the guarantee that exported designs match the latest collaborator save.
Who you’d be doing this for
“My director downloaded the deck after I approved the new slide, and it had the old legal copy again.”
Katerina Alexiou · Content Operations Manager
Coordinates approval and publishing for an enterprise content team using shared presentations and campaign designs.
What is at stake
A growing set of collaborative designs can show an older saved version and export it. You must weigh write availability against a recovery path that proves every exported design is current.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- editing continuity vs design integrity
- capacity growth vs migration safety
- export throughput vs version verification
- fast containment vs durable correction
Why Canva
Collaborative designs and the Chromium-based export pipeline turn a stale read into a file creators can share, print, and publish.
Written with these in mind
Not your kind of problem? 35 more at Canva, 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.