Last FM Not Scrobbling? How to Fix Missing Spotify Plays

Last FM not scrobbling your Spotify plays? Start by checking whether the next few songs appear before changing your connection. A missing entry can reflect delayed display, an interrupted connection, or a wider service problem. Each calls for a different response.

This guide follows Last.fm’s troubleshooting sequence, with a check after each fix. The aim is to establish whether fresh plays are being recorded, then assess the older gap separately. A successful reconnection is useful evidence that tracking has resumed; it does not establish that every missing listen has returned.

Last FM not scrobbling: identify the symptom first

Find the last Spotify track recorded in your Last.fm library and note its approximate time. Then choose the closest symptom below. Treat the possible cause as a starting point, not a diagnosis.

This sequence draws on Last.fm’s official Spotify troubleshooting guide. Work through one change at a time so you can tell which action was followed by a successful test.

Check whether Spotify plays are delayed or missing

Last.fm says Spotify tracks normally scrobble after the following track begins. If an advert intervenes, the previous song may not appear until the adverts finish and music resumes. An album’s final track can also remain unrecorded when nothing plays afterward.

Repeated playback and dragging the progress bar can confuse detection. Local tracks do not display the now-playing or now-scrobbling bar, so that indicator alone is not a reliable test for them.

Use a simple playback check:

1. Note the latest track already visible in your Last.fm library.
2. Play two or three different Spotify tracks without repeating the same song or moving through it manually.
3. Allow the following track to begin before checking for the completed song.
4. Compare the library entries with the songs you just played.

If those songs appear, fresh tracking is working. Note any isolated missing entry for later rather than immediately disconnecting everything.

If three or four different tracks remain absent, continue below. Keep the test song names and approximate times: they will help you distinguish a delayed entry from a genuinely new successful scrobble.

Check service status and restart Spotify across devices

Before resetting authorization, check the Last.fm support forum for an acknowledged incident. Its troubleshooting guide identifies both Spotify API outages and Last.fm display problems as possible causes. When Last.fm has received scrobbles during a site outage, it says they will usually appear once the issue is resolved, unless staff advise otherwise.

If you already use another scrobbling source, check whether its plays are appearing. That comparison can help narrow the investigation. Avoid adding several unfamiliar tools just to run this check; keep the test easy to interpret.

Next, follow this restart sequence:

1. Check for Spotify updates on the devices you use.
2. Check whether the Spotify web player opens and works.
3. Fully quit Spotify on every device where you use it, including your computer and phone.
4. Wait a few minutes, then reopen the desktop app, following Last.fm’s recommended sequence.
5. Start a fresh track and let the next song begin before checking Last.fm.

If your listening setup involves several devices, our Spotify Connect guide provides related background.

Verification is the same as before: look for the completed test track in your library. If it appears, record that tracking resumed after the restart. If an outage is confirmed, follow staff updates before making further account changes.

Reconnect Spotify Scrobbling in Last.fm

If restarting does not help and there is no confirmed outage explaining the problem, try the standard reconnection. Last.fm recommends this after roughly 15 minutes or three to four tracks without incoming scrobbles.

1. Open your Last.fm application settings.
2. Find Spotify Scrobbling and select Disconnect.
3. Wait five minutes.
4. Select Connect and follow the authorization instructions.
5. Start a new Spotify track rather than resuming the one you paused.
6. Let that track finish and the following song start, then check your Last.fm library.

There is also a relevant authorization change in 2026. Spotify’s refresh-token announcement introduced a six-month lifetime for these tokens, with enforcement for existing apps beginning July 20, 2026. Renewing an access token does not extend that lifetime; the user must authorize the connection again.

That makes expired authorization a reason to investigate, especially when Last.fm displays a connection-expired message. It does not prove that every interruption comes from the token policy.

If the standard reconnection fails, Last.fm describes a deeper reset:

1. Return to Last.fm application settings and select Disconnect beside Spotify Scrobbling.
2. Log out of Spotify, then fully quit the app.
3. Open the Spotify account’s Apps page. If the Last.fm scrobbler is still listed, select Remove Access.
4. Wait 15 minutes.
5. Return to Last.fm application settings and select Connect beside Spotify Scrobbling.
6. Complete authorization, reopen Spotify, and log in.
7. Play a fresh track, allow the next one to begin, and check your library again.

Spotify confirms the Apps page and Remove Access control in its app-access instructions.

If the connection page itself returns an error, Last.fm support suggests another browser, a private browsing window, or another network, then trying later if necessary. Note the error rather than treating an unfinished authorization as a completed reset.

Verify that new tracks are being recorded

After reconnecting, focus first on playback that began after authorization finished. Checking only yesterday’s missing songs cannot tell you whether the current connection works.

Use this small test log:

1. Write down when you completed the reconnection.
2. Start a different song from the beginning and note its title and artist.
3. Let it finish and allow the next track to begin.
4. Check whether the completed track appears in Last.fm.
5. Repeat with another different song to check that tracking continues.

If both entries appear, you have evidence of resumed tracking. Then inspect the older gap separately. If fresh songs remain absent, record that result for support instead of repeating the same reset without keeping track of what happened.

Be precise about partial success. “Two new tracks appeared, but yesterday evening is still missing” describes a different problem from “nothing appears after reconnecting.” That distinction helps you choose the next action and prevents an old gap from obscuring a successful repair.

Can missing Last.fm scrobbles be recovered?

Some recent plays may return, but complete historical recovery is not guaranteed. Separate three situations before deciding what to do.

Received but not displayed: Last.fm’s troubleshooting guide says scrobbles received during site outages usually appear after the problem is resolved. In this situation, wait for the incident update and then inspect the affected period.

Recent Spotify plays available after reconnection: In its Spotify refresh-token support thread, Last.fm support says it can retrieve up to your last 50 Spotify plays. Treat that as a limited recovery possibility, not a promise to restore an entire day, week, or longer gap.

Older plays that remain absent: Last.fm’s guide mentions manually rescrobbling a missing entry. However, its scrobble API documentation lists rejection reasons including timestamps that are too old or too new and a daily scrobble limit. Unrestricted historical backfilling is therefore not something to assume.

Before considering manual entries, check which songs have already returned. Keep a list of what is still missing, using listening records you actually have. Avoid reconstructing exact times from guesses or submitting the same listen again while you are still checking recovery.

A useful recovery note separates the confirmed missing interval, the entries that returned, and anything you cannot verify. It is fine for that final category to remain uncertain.

What to include when contacting Last.fm support

If the checks fail over several hours or days and no general incident explains the problem, Last.fm recommends opening a support topic with specific details.

Prepare the information its guide requests:

• Your Spotify username.
• Your Spotify app version, after checking for updates.
• The last Spotify track successfully recorded by Last.fm.
• A recent Spotify track that failed to scrobble.
• Approximately when tracking stopped.

Add a short account of your tests: whether restarting every device helped, whether authorization completed, and whether any fresh tracks appeared afterward. Include the approximate test times and your time zone to make the sequence easier to follow.

Describe any error message accurately. Also distinguish an authorization-page failure from successful authorization followed by missing plays. Those observations give support more to investigate than a report that scrobbling simply does not work.

Check your listening stats while troubleshooting

If your immediate goal is to explore your listening data, Free Your Music’s free Spotify Stats is an optional next step. Free Your Music Stats is free, available any day of the year, and covers 20+ music services.

Use it as a separate listening-data destination while you investigate Last.fm. It is not a fix for the Spotify-to-Last.fm connection or a way to restore missing scrobbles. Keep the repair checklist focused on verifying new Last.fm entries and assessing the historical gap.

For broader guidance, see how to see your Spotify stats and listening history. Start with the question you want answered: whether new plays are being saved, which older entries are absent, or what your listening data shows. Each deserves its own check.