@Convaiyer, let's talk about it. I just sent you a PM.

@Convaiyer Every trigger has a Paywall button. I've had no luck thinking of a way to use it because who wants to pay me to run a command on my own PC? I mean, you'd have to pay me to play Fortnite but other than that

@Ron-Hoskins, I upgraded your account to subscribed for now, just so we can troubleshoot this.

The Runs list does not get updated when you're not subscribed and try to run more than one command per minute. Now that your account is subscribed, you should be able to see what command is running more than once per minute.

Let me know what you see please.

@rsxyo, you could try this old mac version. I don't have Yosemite to test it myself, but it might be old enough.

https://triggercmdagents.s3.us-east-1.amazonaws.com/TRIGGERcmdAgent36.dmg

@Strahan, I wonder if when the TC agent runs your batch file, the sql.exe file isn't in your PATH, so it doesn't run. The agent is probably running your batch file, which you've basically already proven with your loghealth.bat experiment.

I like that you added another line to your laundryreset.bat file that writes something to a log file, but it's writing your log.txt file to the present working directory, which in the context of the TC agent is something like this:
C:\Users\russ\AppData\Local\triggercmdagent\app-1.0.47\resources\app\src

Assuming it is running your laundryreset script, you can probably fix this if you put the full path to your sql.exe file (and your log file) in the laundryreset.bat file, something like this:

@echo off
c:\full\path\sql.exe homecenter "delete from activeitems where action = 8192" /u service.triggercmd.homecenter /p (pwd) /h lioth.mydomain.com /l c:\logs\laundryreset.log
echo From laundryreset.bat >> c:\logs\laundryreset.log
dir >> c:\logs\laundryreset.log

You'll want to remove the last 2 lines, especially the dir line, but I put it there because that can show you what the working directory is.

@Ron-Hoskins, I'm glad you figured it out. No need for a donation - I hope you'll subscribe at some point.

@Rodrigo-Carvalho-0, those emails are meant to tell users who don't have a TRIGGERcmd subscription why their command didn't run.

You must have an Alexa routine that's trying to run multiple commands every hour. Could you disable or delete that routine?

Otherwise, I could add an option in your profile page for non-subscribers to disable those emails - they'll just silently fail because you're not subscribed and you're trying to run multiple commands in 1 minute.

@Moacir-Vilela-Sêga, I just uninstalled and re-installed the background agent. I'm using the latest version of the agent - 1.0.47.

You could try rebooting, then trying again.

@chrischickshow, that makes sense. I'll add something about that to the docs to warn people not to use the name of a room in their voice words..

@Moacir-Vilela-Sêga good. Sorry I didn't get back to you but I did test it and it was still working for me.