Command edits not pushing to site/skill

[StoneColdCole]

Hi,

Today I've tried to rename the spoken computer name of one of my computers in my account, but in my Alexa device list the spoken command didn't change.
I tried to delete the computer and add it again, which didn't resolve the issue and brought up another issue:
Edits to my commands.json file have not pushed/published to my TRIGGERcmd account. The only command available is to open Gnome.

This is my commands.json:

[
{"trigger":"Reboot","command":"shutdown -r","ground":"foreground","voice":"reboot","allowParams": "false"},
{"trigger":"Shutdown","command":"shutdown -h now","ground":"foreground","voice":"shut down","allowParams": "false"},
{"trigger":"yum update","command":"yum -y update","ground":"foreground","voice":"yum update","allowParams": "false"},
{"trigger":"apt update","command":"apt-get -y update","ground":"foreground","voice":"update","allowParams": "false"}
]

Is there an outage on the website side?

[Russ]

@StoneColdCole, there's no outage on the webside side. I just tested it.

Are you running Linux or Raspberry Pi?

I wonder if you have two commands.json files - one in your user's /home/(username)/.TRIGGERcmdData folder, and another in the /root/.TRIGGERcmdData folder. Can you check that for starters?

You might have installed the background agent that's using the /root/.TRIGGERcmdData folder.