The "idle" message is showing because arpReach is currently in between tasks.
For example, the arpReach script ran its last task at 7:05 PDT (and has already finished all the due tasks for that run) and will run again at the next defined run time of your cron job for the arpReach script (we recommend it to run every 5 minutes, but you can really set it to whatever you want on your server).
If your cron job is set to run every 5 minutes, the next idle time would show up after the task was finished running at 7:10, then 7:15, then 7:20, and so on.
The status will change to "running" if it’s currently sending out follow-up messages and broadcasts, retrieving bounces, etc., but will go back to idle once it’s done doing all these things.
How do you know if there’s something wrong:
- If it indicates that the scheduled task has never ran
- If the last time it ran was not "current" (or if it appears to be stuck on a past date and/or time)