TRIGGERcmd - Your command didn't run
-
Having issues with getting errors that a trigger didn't run but they actually did. This has been happening from the start.
10:41AM
Hi Michael Murphy,
You tried to run a command on INTEL-NUC7i7BNHXG, but your TRIGGERcmd agent doesn't seem to be connected.
The agent should have responded with a "Command ran" entry in the Runs list for OpenArlo, but it didn't.
Please restart the agent and try again.Runs for OpenArlo
Created On
Command ran Thu May 28 2020 10:41:07 GMT-0500 (Central Daylight Time)
Trigger sent from IFTTT Thu May 28 2020 10:41:04 GMT-0500 (Central Daylight Time)Thanx, Michael
-
@Michael-Murphy, thank you for reporting this. I was actually worried people were getting that email when they shouldn't, but you're only the second first person to report it, so thank you! If thought the first person's issue was a one-off, but apparently not.
I think fixed it just now, but anyway I decided to make it an opt-in feature instead of emailing by default.
Now you'll see this checkbox in your profile, and it's unchecked by default:
