My company uses an ERP with API integration to METRC to manage our cultivation business area and it seems like there's an issue where only the users who have TTT installed keep having their user API keys regenerate, which invalidates the old key and they can't do their work. We're in states that require individual API keys are used instead of a master key, otherwise, i wouldn't use individual keys.
At first, i wrote it off as a coincidence, but it keeps happening and i was able to have one of my team duplicate the issue. They installed TTT on their browser on 2/2 and by today, their API key was different and we know they didn't hit the generate button.
Our users love TTT, so i want to try to fix this. Does anyone know how this is happening and if there's any way to stop the key regenerations?
- MMatt Frisbie @mattfriz
Hi Melissa
I'll push a fix for this right away. TTT generates an API key when it detects there isn't one, but this behavior isn't needed anymore (and apparently has issues) so I'll just get rid of it.
I'll follow up when it's ready.
- MIn reply toMbeckett⬆:Matt Frisbie @mattfriz
The fix for this is in 0.16.2, available now.
Browsers will usually get the update within 24 hours. If you want it right away, follow the instructions here: Updating Track & Trace Tools
Thanks for the bug report!
- Progresswith handling this problem