Hi, loving the idea of this package so wanted to give it a go.

We've got around 15 custom commands which are registered in the Console/Kernel.php and we run via the normal laravel scheduler.

However none of these commands are showing on the Totem create task screen.

Is there something we need to do to make these show?

Thanks

Just switching from manually scheduling tasks into Totem. Everything is imported and php artisan schedule:list shows all commands correctly. However none of the commands run at their scheduled time, though manually executing through Totem does work.

Trying to debug locally if I create command to simply log an output, it shows up in list:

• Enabling the command in Kernel.php logs to the log file correctly
• Enabling the command in Totem does not log anything from the command
• Enabling the command in both Kernel and Totem shows identical commands scheduled (see below)

Not sure if there is other configuration missing why this isn't working?

Laravel Framework: 8.34.0 Laravel Totem: 8.1.1

According to the config and the code I can't seem to find a way to disable the Log::info calls being made, which is quickly filling up the laravel-logs which is undesirable for big projects. This is just after enabling totem for 30 minutes in our system:

In our environment, none of our tasks are getting executed anymore. On the page, we have tasks (just a sample of our tasks):

But notice that the only task that appears to be executing anymore is the Download TV Guide. Which was one of the first tasks added to the system. Most of our tasks look exactly the same: 8/31 was their last execution. Even though they have upcoming scheduled times. This includes tasks that are supposed to run every minute.

However, the console command:

Lists nothing.

This morning, I ran a composer update to see if it would fix the problem, and no issues with the update. But tasks still aren't running. I checked my crontab:

* * * * * * php /var/www/html/scheduler/artisan schedule:run >> /var/www/html/scheduler/storage/logs/schedule_runs.log 2>&1

Which writes to a log file so we can make sure everything is running. And the scheduled task runs.

Any of the tasks on the page can be run manually by hitting the play button.

Hey,

after installing and executing "php artisan migrate" i´am getting the following error:

The point is following migration, which don´t work on postgresql:

Creating at new task: in the field "PARAMETERS (OPTIONAL)" I insert the following information for a custom command that can accept multiple arguments: "seaport=15 typetraffic=05" When i click Execute (to force execution) it works, because it don't use the console. However, when using the console (Laravel's schedule), it errors. I took the liberty to debug the code and found a problem in the file Task.php, method compileParameters. The problem happens because when running on console it doesn't pass named parameters, and in the mentioned method it will override the first parameter with the second as both will have the key 0. Following is a Print of a fix.

Please inform me if there is another solution.

Right now in the \Studio\Totem\Providers\ConsoleServiceProvider::register method the booted event is being listened and then app is run in console, then new schedules are added into application.

Proposing to simplify this by:

1. using \Studio\Totem\Providers\ConsoleServiceProvider::boot method instead of \Studio\Totem\Providers\ConsoleServiceProvider::register method
2. do the $this->app->resolving(Illuminate\Console\Scheduling\Schedule::class, function (...
3. don't check for console

This way whoever wants the schedule class would get it with all schedules already added.

Not sure though how this thing could be tested or if resolving events are triggered in unit tests.

Every request made outside of Totem routes still has totem queries such as:

select
  *
from
  `totem_task_frequencies`
where
  `totem_task_frequencies`.`task_id` = 1
  and `totem_task_frequencies`.`task_id` is not null

and

select
  *
from
  `totem_frequency_parameters`
where
  `totem_frequency_parameters`.`frequency_id` in (1)

Is there a reason these queries and cache hits are running on all requests?

Hey,

I am trying to run it with the comand route:call and using this as parameter: /api/v1/test?api_key=1234567890

The response is The "/api/v1/test?api_key" argument does not exist. Note that the api_key values is omitted on the error message.

The same command: php artisan route:all /api/v1/test?api_key=1234567890 runs on the command line.

What am I missing?

Thanks,

1. I've created new project on fresh Laravel 5.8.*.
2. I've added "studio/laravel-totem": "^5.0" to composer.json, nothing else.
3. Then I've created new task to scheduler using Totem form:
4. I've already had schedule:run in crontab: ** totem/artisan schedule:run >> /dev/null 2>&1 **
5. Tasks not firing, because php artisan schedule:list returns only No Scheduled Commands Found

I'm using latest MacOS, PHP 7.3.* and MySql 5.7.*. I've already tried to

• clean cache,
• optimize,
• create new Laravel fresh project only for Totem tests,
• change between different databases,
• create own config/totem.php file with empty configuration.

Nothing helped.

Do I need any special configuration in .env or database.php/cache.php files?

Hello i am working on laravel 5.6 and i am using totem "studio/laravel-totem": "v3.3.1". the issue is totem task is not firing. i have checked with every minute schedlue task and between but no luck. and all my kerrnal task is running

please help me i need this is working urgently

Somehow in version 9 totem is missing auth guard, it keeps redirecting to login and due to loged in user it keeps redirecting to /home. I did configure AppServiceProvider.

Hi I checked your code and notice that you get list of artisan commands with Artisan::all() for display in web UI.

But the Artisan:all() does not return all artisan commands because your code does not running in console.

For example for laravel/telescope package see ServiceProvider.

This provider first check if Laravel is running in console then register commands. But when we call Artisan:all() commands that not return the telescope or horizon commands.

So if you can allow to define custom commands this package will more useful.