The issue mentioned by Anita will only occurs after LF Server is rebooted. It happens on LF 9.2 and later version. If that is your case, the scheduled indexing does not resolve the problem because LF Server will not respect the schedule. The following script may help to resume index queue automatically.
set args = wscript.Arguments
if args.Count = 5 then
lfso = wscript.Arguments(0) 'e.g. LFSO100
serverName = wscript.Arguments(1)
dbName = wscript.Arguments(2)
username = wscript.Arguments(3)
password = wscript.Arguments(4)
set app = CreateObject(lfso & ".Application")
set serv = app.GetServerByName(serverName)
set db = serv.GetDatabaseByName(dbName)
set conn = CreateObject(lfso & ".Connection")
conn.UserName = username
conn.Password = password
On Error Resume Next
if db.IndexStatus.Status = 4 then
For example, you can use
ResumeIndexQueue.vbs LFSO100 localhost repositoryname admin password
If LF Server didn't reboot when you encounter the problem, please check the connection between LF Server and LF Full-Text Search Engine. If the problem persists, please contact your VAR about opening a support case for this.
For your latest reply, the folder you place QuitePeriods.xml is right. The time period seems wrong, where the end time should not be earlier than the start time. If you want to resume indexing every 7:00AM you can set it like <Period>1,6:55-1,7:00</Period> so that indexing will not effect much, or <Period>1,19:00-2,7:00</Period> which will pause indexing in the evening and resume it in next morning.