Daan, we were able to replicate this error with an existing connector. It seems that newly created connectors are not affected by this error. Please create and authorize a new connector instead of the old one and check if the "Fetch email" action works with it.