When you send commands to a Windows, macOS, or Linux device through Swif, those commands might go into one of two queues: the Swif Agent queue or the MDM queue. These queues operate in parallel, which means Agent-based commands and MDM-based commands can run independently. However, each queue processes only one command at a time within its own pipeline.
1. How Swif Queues Commands
1.1 Agent-Based Commands
Typical Examples:
Running scripts
Installing software
Removing local user accounts
Collecting advanced system data
Queue Behavior:
The Swif Agent on the device periodically checks in with the server.
If commands are waiting for the Agent, it downloads and executes them one by one.
Additional commands remain queued until the current command finishes or times out.
1.2 MDM-Based Commands
Typical Examples:
macOS device profile pushes
Remote wipe
Passcode resets
Queue Behavior:
Swif’s MDM server notifies eligible devices (often via Apple Push Notification Service) about pending commands.
The device’s built-in MDM client processes them sequentially.
These MDM commands do not block Agent commands; they run in a separate, parallel queue.
2. Why Commands May Appear “Stuck”
Long-Running Agent Tasks
If the Agent is installing large software or collecting extensive data, subsequent Agent commands stay in the queue. MDM commands, however, can still proceed.
MDM Delays
macOS devices may not process MDM commands until they are online and receive APN notifications.
Timeout
Both the Agent queue and the MDM queue have a default 15-minute timeout. If a command doesn’t complete within that timeframe, Swif marks it as failed, and the queue resets.
3. Understanding “Last Connected”
Swif currently displays only “Agent Last Connected” in the console—showing when the Swif Agent last checked in. MDM commands do not have a separate visible timestamp.
4. Typical Scenarios
Agent Queue Busy, MDM Command Succeeds
A large Agent-based software install is running. You push an MDM profile at the same time.
The MDM command can proceed right away in its separate queue, even though the Agent queue is busy.
MDM Command Delayed, Agent Commands Continue
A macOS device is offline, so MDM commands remain pending. Meanwhile, the Agent can still process its own commands if the machine comes online and the Agent connects.
Deleting a User Triggers a System Refresh
After a “delete user” command completes, Swif recognizes a system change (the user list has changed) and automatically collects updated device information.
Any new commands submitted right after the user deletion might be added to the queue simultaneously (e.g., user deletion finishes, device info collection triggers, plus any user-initiated commands).
These commands then process one by one, potentially causing a short backlog in the Agent queue until each operation finishes or times out.
Last Connected Timestamp “Stuck”
The Agent is mid-command. It won’t update the timestamp until it finishes or hits the 15-minute timeout.
5. Best Practices
Avoid Overloading One Queue
Try not to stack multiple resource-intensive Agent commands (e.g., large software installs, user changes, data collections) in quick succession.
Plan for Automatic Data Collection
If you remove a user or perform any major system-altering command, Swif may automatically gather updated device info, which can add a temporary command queue step.
Give Commands Time
Large tasks can take several minutes. If they exceed 15 minutes, the system times out the command.
Use Parallelism Wisely
Remember that Agent and MDM commands do not block each other—feel free to push an MDM profile even if the Agent queue is busy.
Keep the Agent Updated
Newer versions of the Swif Agent handle concurrency and system refresh tasks more efficiently.
6. Checking Swif Agent Logs
If commands remain in a queue or fail unexpectedly, checking logs can help pinpoint the cause. See the Swif Data Refresh Guide for more info. Common log locations:
Windows
Event Viewer → Applications and Services Logs → Swif
Or
C:/Program Files/Swifteam/log.txt(path may vary by version)
macOS
/var/log/swif/agent.logor within the Swif install directory
Linux
/var/log/swif/or/opt/swif/logs(depending on your distribution and install path)
You may also enable debug or verbose modes if directed by Swif support.
7. Troubleshooting Steps
Refresh the Console
Sometimes, the UI needs a manual refresh to show updated statuses.
Verify Device Connectivity
Ensure the device is online and can communicate with Swif.
Wait or Reissue Commands
If a command times out, consider reissuing it after confirming the device is ready.
Check Agent Logs
Look for any error messages or warnings that might indicate why commands are stalled.
Contact Swif Support
If commands remain stuck beyond 15 minutes or repeatedly fail, email us at support@swif.ai.
8. Key Takeaways
Two Parallel Queues: Agent commands and MDM commands don’t block each other.
Triggered System Refreshes: Certain commands (like deleting a user) can automatically spawn an additional data collection task, leading to a temporary queue backlog.
15-Minute Timeout: Both queues reset if a command doesn’t finish in that window.
Agent Last Connected: The only timestamp shown in the Swif console, reflecting when the Agent last checked in.
Understanding these behaviors helps you diagnose and resolve any perceived “stuck” commands more efficiently, ensuring a smoother device management experience. If you have further questions, feel free to reach out to us any time!