Monitored Folders Status

The Monitored Folders Status page shows what PlayIt Manager's Monitored Folders feature is doing right now. The upper list summarises every monitored folder and its current scanning state, while the lower Recent events log records the individual actions taken as files are added, changed or removed.

Use this page to confirm that files you have added to a monitored folder were actually imported, and to diagnose why a particular file did not appear in the track library. Where the folder list tells you that a folder exists, this page tells you when it was last scanned, what that scan found and exactly which files were affected.

To open this page, click Monitored Folders Status on the Listing Monitored Folders page. You need the Can add, edit and delete monitored folders permission to see it.

Rescan All

At the top of the page is a button bar containing a single Rescan All button, used to scan every monitored folder immediately, without waiting for the automatic countdown. This is the quickest way to confirm that a file you have just added or fixed is now being picked up. New activity appears in the Recent events log for the selected folder as the scan runs.

Monitored folder list

The monitored folder list is a grid with one row per monitored folder. Select a row to show that folder's activity in the Recent events log below. The columns are:

Column	What it shows
Path	The folder being monitored.
Status	The folder's current state: Idle (waiting for the next scan), Scanning (a scan is in progress) or Disabled (the folder has been disabled and is not monitored).
File Count	The number of files found in the folder during the last scan.
Last Scan Duration	How long the last scan took, for example `5.123s`, or with a minutes part such as `1m 2.500s` for a longer scan.
Last Scan Summary	What the last scan found, for example `2 new track(s); 1 changed track(s)`, or `No changes` if nothing changed.
Next Scan In	A countdown to the next automatic scan, in seconds.

Recent events

Below the folder list is a log of the individual actions taken for the selected folder as files are added, changed or removed. Where the folder list tells you the summary of the last scan, the events log tells you exactly which files were affected and what happened to each one.

Select a folder in the upper list to see its events; a folder is selected automatically when the page opens. The log shows the most recent events for that folder, newest first, and updates automatically as new activity occurs. If the selected folder has no recorded activity yet, the log reads No recent events for this folder. The columns are:

Column	What it shows
Time	The date and time the event occurred, shown in your server's time zone.
Type	The severity of the event: Info, Warning or Error.
Message	A description of what happened, usually naming the file involved.

The Type of each entry tells you how it went:

Info: a normal monitoring action completed successfully. Examples: Adding track from file: <name>, Updating track from file: <name> and Deleting track: <name>.
Warning: something was skipped or needs your attention, but monitoring continues. Examples: New file is not a track: <name> and Changed file is not a track: <name>, meaning the file could not be loaded as an audio track.
Error: a scan failed. The message includes the underlying error, for example Scan failed.

The page refreshes automatically while it is open: the status data is reloaded every few seconds, and the Next Scan In countdown ticks down each second.

A folder scan can repeatedly report new files. This happens when a folder contains files that are not valid audio tracks: because they are never added to the track library, each scan treats them as new again. The Recent events log makes these files easy to spot. Look for Warning entries such as New file is not a track.

The events log lists only recent activity for live troubleshooting; it is not a permanent audit trail. Only the most recent events for each folder are kept.

Example: finding out why a file did not import

Suppose a presenter copies a new jingle into a monitored folder but it never appears in the track library. Open the Monitored Folders Status page and select that folder in the upper list. In the Recent events log you might see a Warning entry reading New file is not a track: jingle-final.wav.

That tells you the file was detected, but PlayIt Manager could not load it as a track, usually because the audio is corrupt, the format is unsupported, or the file is still being copied. You can then re-export or re-copy the file and click Rescan All to try again, watching the log for an Info entry such as Adding track from file: jingle-final.wav to confirm it imported.