Google Team drive - 403 error

Welcome to the forum @genitguy3

Odd behavior from storage destinations is often not readily explained, and Team Drive seems rare.
I suppose you could try careful lower level testing using Duplicati.CommandLine.BackendTool.exe.
Duplicati.CommandLine.BackendTester.exe can do automated tests, starting with an empty folder.
They both use a Target URL which you can get from Export As Command-line. Your posts show a
delete operation failing, but I’m not sure if others fail. Recreate would be running lots of get ones.

Using those two command line tools, you can either pick the operations or have Duplicati run them.

Any idea what changed?

EDIT:

Google does have some odd permission rules where Duplicati can usually only see files that it made.
Was troubled duplicati-be6b859c8dd45416a8af093be6c91e1fe.dblock.zip.aes finally deleted?
If not, I suppose you could look at it to see who created it. Be careful if moving files in by hand though.
If you had done that, though, I’d have expected a delete error on a dlist unless you keep all versions.