I wonder if there is some sort of timing issue here or “recovery issue”
Can you remove one letter from the api key and then add one and see if it starts working?
@Falco I wonder if we just treat it as “configured” as soon as an API key is there. At that point you can look at logs to see if it breaks.
The test on config is incomplete anyway… API could be temporarily down, Key could expire a week later and it is still (configured), I think this is just too complicated, we should just remove the check and trust logs here.
Having a dashboard warning that triggered when the API key failed would be good. I’ve seen several people (including myself) configure things correctly except the service wants more cash.
In fact, I use those same APIs with other services such as a php script, a wordpress plugin, and they work without problems; but I don’t understand why when I put it here, it is not activated, I don’t know if I have to configure something additional, in addition to putting the api.
I have also put the name of the organization and removed it (although it says it is optional).
Friend, I was able to solve it. I needed to pass the basic code again so that the configuration would be applied (I thought it was only necessary to install it)