> ## Documentation Index
> Fetch the complete documentation index at: https://cloud.laravel.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix Production Command Failures

> Resolve production command failures in Laravel Cloud when commands prompt for confirmation in non-interactive environments.

Some migration operations are destructive, which means they may cause you to lose data. As all Laravel Cloud environments default to `APP_ENV=production`, you may run into issues running migrations in an ad-hoc manner using the "Commands" tab from your environment panel. Since these commands do not support interactivity, the command will fail if it attempts to prompt you for input. This happens most commonly when attempting to run migrations in a production environment.

```shell theme={null}

                           APPLICATION IN PRODUCTION.


   WARN  Command cancelled.

```

If you are comfortable with the risks associated with running migrations in a production environment, pass a flag to bypass the production environment warning.

<Tabs>
  <Tab title="Laravel">
    Append the `--force` flag to bypass the production prompt:

    ```bash theme={null}
    php artisan migrate --force
    ```

    Related commands which may also require the `--force` flag include:

    ```bash theme={null}
    php artisan migrate:fresh --force
    php artisan migrate:refresh --force
    php artisan db:seed --force
    ```
  </Tab>

  <Tab title="Symfony">
    Append the `--no-interaction` flag to bypass the production prompt:

    ```bash theme={null}
    php bin/console doctrine:migrations:migrate --no-interaction
    ```

    Related commands which may also require the `--no-interaction` flag include:

    ```bash theme={null}
    php bin/console doctrine:migrations:migrate --no-interaction --allow-no-migration
    php bin/console doctrine:schema:update --no-interaction --force
    ```
  </Tab>
</Tabs>

### Customizing your `APP_ENV`

If you are working on a non-production environment, you may consider overwriting your `APP_ENV` environment variable in your environment's [Custom Environment Variables](https://cloud.laravel.com/docs/environments#environment-variables) to better match your environment's purpose. Non-production environments will not trigger the same warnings as described above.

```
APP_ENV=development
```