Yes we do. However we tried again this morning and despite still having that restriction in place, we're no longer getting that error message. It seems like this was a temporary bug that's now been resolved.