2 out of 4 computers have stopped running Commands

Mike Vecchiarelli

Hi,

I have 4 computers. They all have like commands. I run commands via API calls through Zapier and Pipedream.

All computers are receiving triggers (validated through the logs). But, as of yesterday, 2 of the computers have stopped running the commands that are sent...despite receiving the triggers from their source.

Why would this happen? What would you need to see to support me with this. Getting this up and running again is quite important for me.

Thank you!

Russ

@Mike-Vecchiarelli, have you tried restarting the agent on the 2 that are not working?

Does it work if you use the Trigger button on the website?

Please confirm the commands are all foreground commands, unless you're using the background agent.

Do the commands work if you run them using the green "play" button in the GUI Editor?

Mike Vecchiarelli

@Russ All foreground. It looks as if the computer had 3 TriggerCMD programs running (in the Task Manager) and that it had gone offline.

What would cause this and how can I prevent it?

Russ

@Mike-Vecchiarelli, did you fix it by restarting the agent?

One place to look for clues is your C:\Users[your user]\.TRIGGERcmdData\debug.log file.

One idea is your antivirus software could have broken the agent. If so, you could try excluding the C:\Users[your user]\AppData\Local\triggercmdagent folder to prevent that.

If the computers lost internet temporarily, the agent should have auto-reconnected when the Internet came back, so I don't think that's it.

FYI, it's normal to see 3 instances of the TRIGGERcmdAgent.exe in task manager under Details.

Please tell me if it happens again. If the agent has a bug I definately want to fix it.

Mike Vecchiarelli

@Russ It's been a bit where the issue didn't happen, but it seems to have occurred again. In this instance, the following happened...

I have an automation that will run from Zapier, part of it being a call to TriggerCMD. I checked the Zapier logs and see that I got a 200 response. I checked in the TriggerCMD logs and see that the Trigger was sent, but it was not Run. Let me know if there is some information I can provide that would be supportive of getting an answer to the issue that's occurring.

Seems like from time to time the commands are received but don't run.

For context, this entire thread would have the same context - running something from Zapier to TriggerCMD (as part of a longer list of activities).

Anything you can do to support in quick order would be greatly appreciated! Thanks!

Mike

Russ

@Mike-Vecchiarelli, sorry about the trouble. Please confirm this: in the command's runs list, you see "Trigger sent" but you don't see the corresponding "Command ran" entry, correct?

Also, did it stop running commands after that point until you restarted the agent? Or did it auto-correct itself and you see the "Trigger sent", "Command ran" pattern resumed after that initial missed run?

I'm trying to figure out if the agent malfunctioned and stopped running commands, or if it just missed that one command. The root cause will be very different depending on the answer to that question.

Also, can you check you debug.log file for any errors and send it to me? You can find it in c:\Users\(your user)\.TRIGGERcmdData.

Mike Vecchiarelli

@Russ See below for a visual reference...

Trigger was sent. No command had ran. (referencing 5th row down - Mar 13 2024 13:18:05)

Restarting it was not required in this case - it continued to run for other cases afterward.

This is for a client of mine and I will try to retrieve the log asap.

Russ

@Mike-Vecchiarelli , can you send me a copy of your debug.log file?

I wonder if you see multiple instances of something like this:

  |>    Now connected to https://www.triggercmd.com.
\___/   For help, see: http://bit.ly/2q0QDpf
        (using sails.io.js node SDK @v1.2.1)
         Connected at: Fri Mar 15 2024 18:24:00 GMT-0400 (Eastern Daylight Time)

Also, can you tell me the versions of the agent on your 4 computers? If they're different, that could be a clue.

Also, I have better logging now, so I can probably track down the server logs related to your issue if you give me the time and your computer ID or account email address if/when it happens again.