Deep Dive into Eloquent Issues: Debugging Dynamic Method Calls?

Following up on a recent 'Call to undefined method' debugging session, I'm now facing a more nuanced problem with dynamic Eloquent method resolution within a complex service layer.

The core of the current eloquent issues stems from attempting to dynamically call a custom Eloquent scope (or even a relationship method) on a model instance that's been passed around through several layers of abstraction. While direct calls work, dynamic invocation using call_user_func_array or similar patterns results in an unexpected 'Method not found' error, even when __call and __callStatic should theoretically intercept. This is where the Laravel method resolution becomes tricky.

• Verified the scope/relationship exists and works when called directly on the model.
• Dumped $model->__get('relations') and $model->getGlobalScopes() to ensure everything is loaded.
• Traced execution through Illuminate\Database\Eloquent\Builder::__call and Illuminate\Database\Eloquent\Model::__call – it seems to bypass the expected resolution path under dynamic context.
• Experimented with app()->make() and service container resolution, but the issue persists when the method name is a variable.

Expected vs. Actual: Expected: call_user_func_array([$model, $dynamicMethod], $args) should resolve to the Eloquent scope/relation. Actual: BadMethodCallException: Call to undefined method App\Models\MyModel::dynamicScope().

// In MyService.php
public function fetchData(MyModel $model, string $scopeName, array $args = []){    // This works: $model->myHardcodedScope()->get();
    // This fails:
    return call_user_func_array([$model, $scopeName], $args)->get();
}

Error Log:
[2023-10-27 10:30:00] local.ERROR: BadMethodCallException: Call to undefined method App\Models\MyModel::myDynamicScope.
in /path/to/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:1234
Stack trace:
#0 /path/to/app/Services/MyService.php(50): Illuminate\Database\Eloquent\Model->__call('myDynamicScope', Array)
#1 [internal function]: App\Services\MyService->fetchData(Object(App\Models\MyModel), 'myDynamicScope', Array)
...

Is there a specific way Eloquent's magic methods (__call, __callStatic) interact with call_user_func_array or ReflectionMethod that prevents dynamic scope/relation resolution, especially when the model instance is passed around? Or am I missing a crucial piece of the Laravel query builder or eloquent builder internal dispatch mechanism for Laravel method resolution?

Thanks in advance for any insights!