ARC Shutdown Seat Error

The editor didn't show my pop up screenshot that I attached. Here it is:

That is a really strange popup to see during shutdown. We’ll see if it can reproduced and get back to you

@Customer Support. I've done some more thinking on what lead up to this popup and some troubleshooting on my end. However this issue pursuits

More bits of information on events that I did after the last ARC update before I first saw this issue:

• As stated above, this pop up that stalls ARC shutdown didn't happen till after the last ARC update. I downloaded it, installed the update (which included the new AI assistant).
• After the update I released the one of my two seats. I released the one that held my robot's onboard computer (called Robot_Brain). Then I added a different computer running ARC so I could test the new AI feature without having to remote in to the robot's computer.
• On the new computer, I updated ARC to the latest version.
• After removing the robot's computer from my Synthiam account and adding the new computer (with updated ARC) I again had both (2) seats full.
• I then proceed to test my working ARC project (the same one that runs the robot) on the new computer. It was not connected to the robot or any EZB's. I bought some AI credits and tried the new AI on this computer. Everything ran like expected. ARC started up and worked. All my controls and scripts loaded and the AI feature worked just fine. Shutdown was as expected with no pop up or stalled ARC Shutdown.
• I then went into my Synthiam account and removed the new computer to free up the second seat.
• I started up the robot and it's onboard computer started up. ARC auto launched and (at startup) the pop up appeared asking this computer to be added to my account. I clicked yes and ARC and the robot started up as expected.
• The robot ran for a few hours trouble free.
• I can't remember if I got the pop up that stalled ARC's shut down at the end of this session when I powered down the robot. If not it was the very next time I ran the robot and tried to power it down.

Here's a couple more things that I've tried since.

• I tried to remove all computers to both seats on my account. Then just re-add the robot's onboard computer (Robot_Brain). Thus just having one seat filled. No change. ARC starts up and runs properly but I get this pop up and ARC Stalls on shutdown.
• I uninstalled ARC on the robot's computer, re-downloaded and re-installed it. No change.
• I can (remotely) shut down ARC by clicking the "X" in the upper right corner. ARC will close scripts and controls and shut down properly with no pop up or stall. I can then (remotely) shut down Windows which will auto power down this on board computer.
• It seems that the only time I get this pop up at shutdown and an ARC stall is when I use the Shutdown(PC) command. The script holding this command will run and execute all commands in it but after the Shutdown(PC) command is sent ARC stalls. Here's the shutdown script I use;

ControlCommand("Personality Generator", "PauseOn");
sleep(250);
ControlCommand("Head Section", "ScriptStart", "Bubble Full Up");
ControlCommand("Head Section", "ScriptStart", "Radar 1/4 Sweep");
ControlCommand("ADC Watcher", "ScriptStop");
ControlCommand("Weather Loop", "ScriptStop");
ControlCommand("Script Manager", "ScriptStop", "Power Pack Pull");
ControlCommand("Connection Check Monitored", "ScriptStop", "Connection Check");
var Goodbye = Utility.getRandomUnique(1, 12);
print("Goodbuy: " + Goodbye)
if (Goodbye == 1) {
ControlCommand("Soundboard v4", "Track_9");//say "Hasta La Vista"
sleep(2500);
}
else if (Goodbye == 2) {
ControlCommand("Soundboard v4", "Track_10");//say "Love Long & Prosper"
sleep(2750);
}
else if (Goodbye == 3) {
ControlCommand("Soundboard v4", "Track_36");//say "So it Goes"
sleep(2500);
}
else if (Goodbye == 4) {
ControlCommand("Soundboard v4", "Track_83");//say "Pleasure to Serve"
sleep(3500);
}
else if (Goodbye == 5) {
ControlCommand("Soundboard v4", "Track_84");//say "Goodby"
sleep(1750);
}
else if (Goodbye == 6) {
ControlCommand("Soundboard v4", "Track_91");//say "May the Force be with you"
sleep(2750);
}
else if (Goodbye == 7) {
ControlCommand("Soundboard 2", "Track_19");//say "My Power Pack needs charging"
sleep(4500);
}
else if (Goodbye == 8) {
ControlCommand("Bender", "Track_28");//Say "Shows Over"
sleep(3000);
}
else if (Goodbye == 9) {
ControlCommand("Bender", "Track_36");//Say "Wanna Kill All Humans?"
sleep(3500);
}
else if (Goodbye == 10) {
ControlCommand("Bender", "Track_30");//Say "So Long Coffin Stuffers"
sleep(3500);
}
else if (Goodbye == 11) {
ControlCommand("Bender", "Track_3");//Say "Bite My Shiny Ass"
sleep(3500);
}
ControlCommand("Head Section", "ScriptStart", "Bubble Full Down");
ControlCommand("Left Arm", "ScriptStart", "Left Claw Closed");
ControlCommand("Right Arm", "ScriptStart", "Right Claw Closed");
sleep( 1000 );
Utility.shutdownPC();

I hope this new info helps you figure what's happening. Thanks for your help!

That makes sense. From what I understand, it looks like you are trying to use three copies of ARC with a two-seat subscription. A two-seat subscription allows two copies of ARC to run at the same time. However, you cannot load ARC, release a seat, and then load another copy to work around the seat limit. The system will only allow the number of active copies that your subscription is licensed for.

@Customer Support. The same copy of my project was used in each instance of ARC I was using. Still, how does this explain why this pop-up happens at the end when I want to shut down and hold ARC from shutting down and not at the beginning when I start up?

That behavior is consistent with seat validation happening during shutdown, not only at startup.

A few key points:

• A 2-seat ARC subscription allows two concurrent ARC instances.
• If a third ARC instance is started while two seats are already in use, ARC may appear to open but then surface a licensing/seating prompt when it later validates the account state.
• In your case, the popup appearing during Utility.shutdownPC() suggests ARC is re-checking the subscription state while it’s already in the middle of closing, and that validation is failing or getting confused because the app is being torn down while a seat check is still active.

Why it happens at shutdown and not startup

At startup, ARC can complete the seat claim cleanly.

At shutdown, your script is still running when this line executes:

Utility.shutdownPC();

That tells Windows to begin shutdown immediately, but ARC may still be trying to:

• stop scripts
• close controls
• release/refresh seat token state
• process account/AI-related licensing checks

If ARC now believes the machine is not authorized or the seat state is inconsistent, it can show the seat popup right as it exits.

What to try

1) Make sure only one ARC instance is actually running on that PC

Even if you use the same project, ARC still counts instances, not projects.

Check Task Manager and confirm there isn’t another ARC process still active on the robot mini PC or on another machine using the same seat.

2) Avoid triggering Windows shutdown directly from inside the same ARC instance

A safer approach is to:

1. Run your shutdown cleanup script
2. Wait for all audio/scripts to finish
3. Close ARC cleanly
4. Then let Windows shut down

If possible, use a separate Windows shutdown trigger outside ARC, or launch a small external shutdown helper after ARC exits.

3) Insert a delay before shutdown so ARC can finish closing its own resources

For example:

ControlCommand("Personality Generator", "PauseOn");
sleep(250);

ControlCommand("ADC Watcher", "ScriptStop");
ControlCommand("Weather Loop", "ScriptStop");
ControlCommand("Script Manager", "ScriptStop", "Power Pack Pull");
ControlCommand("Connection Check Monitored", "ScriptStop", "Connection Check");

sleep(3000); // give ARC time to settle

Utility.shutdownPC();

4) Test a minimal shutdown script

Temporarily remove the audio and extra script calls and test only:

Utility.shutdownPC();

If the popup still appears, then we’ve isolated the issue to ARC’s shutdown/licensing interaction rather than your shutdown sequence.

5) Check whether the AI feature changed seat behavior

Since this started after the update that included the AI assistant, it’s possible the new licensing logic is being evaluated differently on exit. That would explain why the issue only began after the update.

Best next step

Please try this test:

• Start ARC on the robot mini PC
• Run a very simple shutdown script that only does a short wait and Utility.shutdownPC()
• See whether the seat popup still appears

If it does, then the most useful detail would be:

• the exact text in the popup
• whether ARC is in online/offline mode at that moment
• whether the robot mini PC is still listed as actively assigned in your subscription portal while ARC is shutting down

If you want, I can also help you rewrite your shutdown script so ARC has a cleaner shutdown path before Windows powers off.

I looked into this to see what could be happening, and maybe I’m misunderstanding - so add any clarification if possible. But from what I understand, you’re loading the arc, removing the seat of that arc, and adding the seat to another pc. Is that correct?

You can have as many copies of ARC per CPU as you like. So two seats mean two separate PCs.

The error is regarding multiple ezbs - so shutting down still says "hey, you're talking to more than one ezb, but this computer doesn’t have a seat anymore."

Removing a seat, even after the ARC is loaded, won’t trick the subscription system.

I could be interpreting the issue differently, so please correct me if I’m missing something.

@DJ, thanks for your help. I appreciate your support. However, I'm not trying to trick the subscription system. I release and add seats online in my Synthiam account when ARC is shut down. I've done this many times in the past over many years. Don't know, maybe I did something different this time. I have only one robot and I'm only one user. I simply wanted to run my ARC project on a different computer to try this new AI without having to remote into the robots onboard computer. Logic would dictate to my brain that once a seat is released I could add any other computer, running any project, as long as I only have two. Maybe I need to buy another seat to keep this from happening.

I think what may be the issue (according to Athena) is that there may be a script that is still running when the shutdown PC command is sent. I have noticed a motor that hasn't totally parked in its commanded shut down position (called by the shutdown script) when this happens and the robot is finally powered down

I'll adjust the sleep command tomorrow and see what happens.

Thanks again for the great service and support.