Common Issues

This page covers common issues and their solutions.

Authentication Issues

”Spotify authentication failed”

Cause: Your Spotify authorization has expired or been revoked.

Solution:

1. Sign out of Playlist Pipeline
2. Sign in again with Spotify
3. Re-authorize the application

”Insufficient permissions”

Cause: The required Spotify scopes were not granted.

Solution:

1. Go to your Spotify Account Apps
2. Remove “Playlist Pipeline” from authorized apps
3. Sign in again and grant all requested permissions

Pipeline Issues

”Playlist not found”

Cause: The playlist ID is incorrect or the playlist was deleted.

Solution:

1. Verify the playlist still exists in Spotify
2. Check that you have access to the playlist
3. Copy the playlist ID again from Spotify (right-click > Share > Copy Spotify URI)

“Rate limit exceeded”

Cause: Too many API requests in a short time period.

Solution:

1. Wait a few minutes before running the pipeline again
2. If scheduling, reduce the frequency
3. For large playlists, consider breaking into smaller pipelines

”No tracks returned”

Cause: The source playlist is empty or filters removed all tracks.

Solution:

1. Check that the source playlist has tracks
2. Review your filter conditions - they may be too restrictive
3. Run without filters to verify the source works

”Failed to save to playlist”

Cause: You don’t have permission to modify the target playlist.

Solution:

1. Verify you own the playlist or have edit access
2. Check that the playlist isn’t a Spotify-generated playlist (these can’t be modified)
3. Try creating a new playlist instead

CLI Issues

”Command not found: plpl”

Cause: The CLI is not installed or not in your PATH.

Solution:

# Reinstall globally
bun install -g @plpl/cli

# Or with npm
npm install -g @plpl/cli

# Verify installation
plpl --version

“Not authenticated”

Cause: You need to log in with Spotify.

Solution:

plpl auth login

“Invalid pipeline file”

Cause: The YAML/JSON file has syntax errors.

Solution:

1. Validate your YAML syntax using an online validator
2. Check for common issues:
   • Incorrect indentation
   • Missing colons or quotes
   • Invalid task types
3. Use plpl validate pipeline.yaml to check for errors

Scheduled Pipeline Issues

”Pipeline didn’t run on schedule”

Cause: Various reasons.

Solution:

1. Verify the schedule is enabled in the web app
2. Check that you have an active subscription (scheduling requires Pro)
3. Check the run history for any error messages

”Missed scheduled runs”

Cause: Scheduler service downtime or issues.

Solution:

1. Check the Status Page for any incidents
2. Manually run the pipeline if needed
3. Contact support if the issue persists

Still Having Issues?

If you can’t find a solution here:

1. Check the FAQ
2. Get Support