
You're finishing a flow the night before a gig and one track — the one that's supposed to bridge the two rooms of your set — just isn't there. You've searched it three different ways: full title, artist name only, the exact spelling off the Beatport tracklist. Nothing comes back. It's a small thing in the middle of a set you've otherwise sorted, but it's exactly the kind of small thing that makes you close the laptop and go finish your prep somewhere else.
Before you do that: a track not being live yet isn't the end of that story, it's the start of a five-minute one. The catalogue is being added to every day — new tracks get analysed and go live continuously, not in some quarterly batch — and the fastest way to get a specific one moved up the queue is to just say so. That's what track requests are for, and the whole process takes less time than the search you just ran.
It helps to know how the catalogue actually grows, because it changes what a missing track means. Nothing here waits for a scheduled update — tracks go in continuously, and a lot of what lands in any given week starts with a DJ asking for it by name. If you can't find something, you haven't hit a permanent hole in an unfinished catalogue. You're just ahead of the queue on that one track, and asking is how you move it up — the catalogue gets built partly by what DJs are actually reaching for mid-prep, and right now that includes you.
You don't need to hunt down a dedicated request page — the prompt shows up wherever you're already searching. Come up empty on the track catalogue, inside Flow Builder, or in Live Mode, and you'll see a search box asking what you're after. Type the artist or title and matches from Apple Music's catalogue show up as you type — tap the right one and the request is filed on the spot, no separate form, no retyping the title. Sometimes that search turns up good news instead: the track's already on Mixgraph, and you're dropped straight onto its page rather than filing a request for something we've already got.
Picking a result this way does most of the precision work for you — you're choosing an actual release, not describing one from memory. If nothing comes back, “enter it manually” is one tap away: artist and title, both required. That's where detail earns its keep. Get the artist spelled the way it appears on the release, not the shorthand you use in your own head, and if you know it's a specific remix or edit, say so — “Original Mix” and someone's bootleg VIP share a title but aren't the same track, and the wrong one landing in the catalogue helps nobody. None of this needs to be a research project, though — if you only know roughly who made it, submit that. A partial request beats not asking at all.
You'll need to be signed in for the request to actually get tracked — search for a track while logged out and Mixgraph still logs the demand, but it can't follow up with someone it doesn't know. And if you're on Pro, that same prompt has a faster route tucked underneath: paste a direct Spotify or Apple Music link and skip typing entirely, or hand over a whole Spotify playlist and Mixgraph requests everything in it that isn't in the catalogue yet.
Once a request lands, it's in the same pipeline as everything else — sourced, analysed for its full chemistry profile the same way every other track on Mixgraph is, then reviewed before it goes live. You don't need to keep checking back manually: you get notified the moment it's in — push if you've got the app, email if you don't — so you can go straight to the track page instead of re-running the same search every few days out of habit.
There's no fixed turnaround time, and it's worth being upfront about that — some tracks go through quickly, others take longer if they're harder to source cleanly or verify. What doesn't happen is your request sitting untouched waiting for some future update. It's in the pipeline the moment you submit it.
The gap doesn't need to stall the rest of your prep. If you already own the track — it's sitting in your Rekordbox collection but hasn't made it into the catalogue yet — import it through Library. Matched or not, it becomes usable straight away: chemistry scored against the rest of your collection using its BPM and key even before it's a fully analysed catalogue track, so you're not stuck waiting on the request just to keep planning.
If the missing track is more of a placeholder — you know the shape of the transition you want, just not the exact track yet — don't leave that slot blank in the meantime. Open Build and describe the set in plain English: the genre, the energy, how you want it to move. You'll get a working draft back in seconds, with something reasonable sitting in that gap for now. Once your requested track lands, you swap it straight in.
And while you're at it, save the tracks either side of the gap to Favourites. It costs nothing and means that the moment your requested track goes live, the surrounding chemistry is already right there waiting — you won't have to go hunting back through search history to remember what you'd planned to sit next to it.
One track not being in the catalogue yet is a five-minute fix, not a reason to shelve the set you're building. Search for it, tap the right result, and get back to the rest of your prep. You can check what's pending and what's landed any time in Track Requests — the request doesn't need your full attention after that; it's being worked whether you're watching or not.
When the track does land, don't just drop it into the slot you originally imagined and assume it'll sit right. Run it through Score My Transition against the tracks either side of it first. Sometimes the track you were waiting on is an even better fit two slots over from where you first planned it — and you'll only know that by checking, not by guessing.
Put these concepts into practice