--- title: "How to Resolve the \"The application is already running. Multiple launches are not allowed.\" Message" slug: "how-to-resolve-the-application-is-already-running-multiple-launches-error" updated: 2026-04-07T08:42:19Z published: 2026-04-07T08:42:19Z canonical: "help.autify.com/how-to-resolve-the-application-is-already-running-multiple-launches-error" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.autify.com/llms.txt > Use this file to discover all available pages before exploring further. # How to Resolve the "The application is already running. Multiple launches are not allowed." Message This document is for iOS devices. ## Situation "The application is already running. Multiple launches are not allowed." is displayed when trying to run `autify mobile link start` ``` [Mobile Link] 2026-02-18T07:30:55.693Z info error: Another instance is already running with PID: 3049 › Error: API connectivity check failed: Failed to access the server › Code: Error Waiting for terminating (forever)... ``` ## Resolution ### 1. Check for dangling processes Try the following troubleshooting steps: 1. Stop all currently active mobile link sessions by pressing `Ctrl + c` 2. Run the following command: ``` ps aux | grep "mobile link start" | grep -v grep ``` 1. Check the output, and note any process IDs (PID) that are shown in the second column In the below example, PIDs would be `68641` and `68628` ``` <Example> autify 68641 0.0 0.1 411668048 66032 s070 S+ 4:55PM 0:00.22 /opt/homebrew/Cellar/autify-cli/0.62.0/libexec/bin/node /opt/homebrew/Cellar/autify-cli/0.62.0/libexec/bin/run mobile link start nYmF1n autify 68628 0.0 0.0 410210544 3312 s070 S+ 4:55PM 0:00.01 bash /opt/homebrew/bin/autify mobile link start nYmF1n ``` 1. Run the following command for each PID ``` kill ``` ※ Please try executing the command after replacing `<PID>` with the ID you confirmed in Step 3. 5. Repeat step 2 to confirm that no other Autify Mobile Link processes are running 6. Run `autify mobile link start` and try NoCode Mobile again