Ewhere enam is one of the ones listed 
E"sorry enam isnt valid, please use enam"
K
HZero-Width Space Time!
CExactly what we have with weur....
E@sdnts this is the error thats happening, providing a region doesnt seem to work and despite the error msg it doesnt accept the new values
Eit only works if i supply
autous-east-1wnam, enam, weur, apac
SOh, thanks for checking, let me look
Ealso thank you whoever let me have tokens that live forever now, it was annoying when this got removed and i had to remember or risk my apps exploding in a year
Eah i see
E
Eone i just made doesnt, only Active
Edid you make those tokens just now? Forever wasnt available until recently
Eor did you edit an existing one?
Eoh yeah
Ethats quirky
Eyep
Efun bug
Ueven a token I explicitly set to 1 year auto selected forever on the edit but saving with forever doesnt remove expiration
Eyeah, edit seems to default to displaying forever regardless of the current value and then not save it
UOne of my r2 tokens is named "r2 token" and I have no idea if I still use it for some reason 
E
UI also have 2 tokens for logpush and idk which one is actually used for my logpush
Ethe bucket i wanted to be in WEUR says its in EEUR
Uhmm this is weird on the profile api tokens view the one named "r2 token" was apparently made by the api instead of the ui?
Eand EEUR isnt even supported for creation apparently
Uand doesnt have any perms?
Erecently made dash R2 tokens just do that now
Ei guess because youre supposed to manage them elsewhere
Uthis was made at least 2+ months ago
Eaws s3api get-bucket-location --endpoint https://<accountid>.r2.cloudflarestorage.com --bucket my-bucketit was made 4 months ago
Eo it looks like the old ones were migrated to this format too
Emine that were normal tokens from back in beta are now showing like this
Euh
Esome of them
Uwhy is it only that token when I have 4
Uyeah
Edeliver me from suffering
E
Uall of my tokens say null for last used on 
Eyeah R2 usage doesnt populate the last used date