Google Drive not letting users play videos, throws ‘allowed playbacks has been exceeded’ error
It has come to our notice that several Google Drive users have been reporting for the past few months that the service is throwing an error while playing videos, stating that the number of allowed playbacks have been exceeded the limit.
Basically, Drive is not letting users play videos regardless of the Web browser or device being used. ‘Unable to play the video at this time. The number of allowed playbacks has been exceeded. Please try again later‘ is the error that pops up while playing a video.
The notification can be seen clearly in the following screenshots shared by a couple of affected users.
A few among those complaining have also added that the ‘Download’ button that appears below the playback exceeded error (see above screenshot) doesn’t work, making the video(s) in question completely inaccessible.
While most of those affected encounter the error while playing videos shared with them, some are greeted with this error notification even for the videos owned by them. Interestingly, users note that the issue appears to be time-dependent, as the ones in GMT- zones can only play the videos in morning, while GMT+ zone users can play them in the evening only.
The issue was first reported this year in June, but caught heat with the onset of September. With multiple users pitching in, an expert finally addressed the affected users on the official Drive forum on September 5, and said
Regarding the issue you’re facing with videos not playing in Google Drive, I’ve made our team aware of this issue and I’ll get back to you as soon as I have an update
They further added on September 6:
I sense the urgency of getting this issue fixed. I’ve already made our team aware of this issue and they are working on it. I will write back once I get to hear from the team
and repeated the same again a few times.
The increasing number of user complaints coupled with the screenshots some of the affected users have shared make it clear that this is indeed an issue. Google has not officially acknowledged the problem yet, but it’s reasonable to say the company is aware of it.
No information yet on whether they are working on a fix, and when it’ll arrive. Meanwhile, keep a tab here, as we’ll keep you updated about all related developments.