@sprince - apologies for the delay in this. We’ll be releasing a fix for this soon and we’ll update this thread when we do.
Google has a habit of updating their apis in a non backwards compatible way, which is what’s happened here. This feature got lost in a migration over to their current api and it wasn’t caught by our tests. Thanks for your patience.