Eloquent debugging headache

hey guys, so i fixed that initial updateOrCreate 'column not found' issue we discussed, it was indeed a missing migration. pushed that through, all good. but now, a completely new, yet annoyingly familiar, 'column not found' error has popped up. it's driving me nuts.

this new one is super weird because it only happens in specific contexts. when i run my test suite, or more critically, when our CI pipeline runs, it fails. but if i just run php artisan serve and interact with the app locally, everything works perfectly. it's like the column just vanishes for CI and tests.

the problem surfaces with a firstOrCreate call on a related model. specifically, it’s when trying to attach or update a user's profile settings. i've already gone through all the usual Laravel troubleshooting steps: checked php artisan migrate:status – all migrations are up, including the one for profiles table. i've manually inspected the database schema directly, the setting_id column is absolutely there, INT(11) nullable. done php artisan config:clear, cache:clear, view:clear, and even composer dump-autoload multiple times. nothing changes this behavior.

// Example of the problematic query
$user = User::find(1);
$user->profile()->firstOrCreate(['setting_id' => $someId]); // 'setting_id' column not found, but it IS there!

And here's the dummy error log:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'setting_id' in 'where clause' (SQL: select * from `profiles` where `profiles`.`user_id` = 1 and `profiles`.`user_id` is not null and `setting_id` = 5 limit 1)

this is the part that's killing me. the column setting_id exists in the profiles table. i can see it. the code works flawlessly on my local php artisan serve setup. it's only in CI (using GitHub Actions) or when i run php artisan test that this 'column not found' error pops up. it's a huge inconsistency and makes this Laravel troubleshooting a nightmare.

any theories on why this inconsistency might be happening? could it be some sort of database connection difference in the test environment vs. local? or perhaps an obscure caching layer that config:clear isn't touching in the CI context? i'm open to any debugging strategies for such an elusive problem.

anyone else experienced this kind of phantom 'column not found' with eloquent debugging?