Carlos E. Oliveira

@shirshak55 You tried use docker (with UNIX distribution) to see if has difference? How much you have memory and how much you specific for each worker?

@shirshak55 You using queue or calling command directly? You use any external service? e.g: redis, mysql, memcached and etc?

I do not see any limitation on the FW. You said that you consume an API, have you checked if the API has limits for simultaneous requests? Did you try...

@shirshak55 No. PHP Cli don't have limitation about instances. Only limitations is your process number (cores) and memory limit. You said API dont't has limitation, okay... but your proxy maybe...

I recommend to read: https://haydenjames.io/php-performance-additional-cpu-cores-vs-faster-cpu-cores/ https://medium.com/@rossbulat/true-php7-multi-threading-how-to-rebuild-php-and-use-pthreads-bed4243c0561 But I think the problem is not in memory/processor. Because the number of limited workers is always the same... 100+. That is, the problem...

Any news about it?

Como esta as permissões de storage? Já verificou o driver de session? Procure mudar o diver de session, ou se tiver driver file, dê corretas permissões nas pastas.

@lucasdealmeida Você pode criar um [observer](https://laravel.com/docs/5.6/eloquent#observers) para o evento de `saving` o qual é anterior a concretização do dado no banco, neste método, valida os dados que estão vindo, com...

Richard, Esta não é uma questão do "laravel", e sim conhecimento de linguagem MySQL. Mas, para recuperar pela chave estrangeira e order pela chave primária. Por exemplo: `$model->whereChave($chave)->orderBy('id', 'desc')->first()` ou,...

Seems like it is related to https://github.com/async-aws/aws/issues/1412 since we see this error when the worker is stopped by the time limit.