Time Restrictions work by cutting off new requests – so cached data or an existing connection
that does not request new data will continue to work until such time as they are refreshed /
reloaded / request new server info.
As an example: time restrictions are set on device A to block internet for 10pm to 7am. A user
on that device is watching a Youtube video – which continues to play after the 10pm ‘off’ time
should start. This is due to the ‘buffer’ for the video which has already been downloaded and
cached. Clicking on a new video or refreshing the page would trigger the time restriction block –
or simply waiting until that video’s buffer has played through and run out.
In the same manner, a user on Device A is browsing their favorite social media site. 10pm rolls
around and the page they are on still functions – the page they are currently on has already
loaded and is not ‘live’ or requesting new information. Clicking to browse anywhere else or
refreshing that page would trigger the time restriction block.
A great way to test that time restrictions are working is to first test that a device is browsing
normally. Then, after creating a time restriction for the device, block out the current hour and
save the restriction. Try browsing again to a new page, which should be blocked. If so, go back
to the Time Restrictions section and edit the ruling to allow internet again for this hour.
Browsing to a new page should again load through properly
To create a Time Restriction for a device, please see the instructions found in the “Time
Restrictions” section of our User Manual.