What is the best way to create a column in production if an issue has occurred?

Here is the migration:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class AddFarmidToUsers extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::table('users', function (Blueprint $table) {
            $table->bigInteger('farmid')->nullable();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::table('users', function (Blueprint $table) {
            $table->dropColumn('farmid');
        });
    }
}

when I run 'php artisan migrate:status' it shows that the migration (above) ran on the date I expected it to run. Should I still do the --force ?

https://imgur.com/YzccLIm here is a view of status on production. i put a yellow arrow next to it. I noticed it today when I checked in code to use the field and it failed with a 500 in production. I opened up pgadmin to look at the production users table and the column is not there. very strange.