Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job execution by user doesn't work #168

Closed
childhomie opened this issue Feb 21, 2023 · 6 comments
Closed

Job execution by user doesn't work #168

childhomie opened this issue Feb 21, 2023 · 6 comments

Comments

@childhomie
Copy link

I've updated to ProcessManager 4.1.1 and Pimcore 10.5.17 and did all migrations.
Job execution by user doesn't work, only cronjobs are running.
I can't find any error in the logs.

@MMierzynski
Copy link

I have the same issue:

  • ProcessManager: 4.1.1
  • Pimocre 10.5.17

@ctippler
Copy link
Contributor

Can you please provide more information? Do you see the jobs in the admin panel and they don't start when you click on execute? If yes -> please check if the xhr request in the network panel returns an error?

Regards,
Christian

@childhomie
Copy link
Author

Can you please provide more information? Do you see the jobs in the admin panel and they don't start when you click on execute? If yes -> please check if the xhr request in the network panel returns an error?

Regards, Christian

Hi Christian,

nothing happens when you click on execute (green arrow) in the admin panel nor the shortcut menu.
xhr request = admin/elementsprocessmanager/config/get-by-id?id=1&_dc=1677153727401 and gets status 200
usually execute follows, but not in this case

{success: true, data: {id: 1, name: "test", group: "", description: "", creationDate: 1676993540,…}} data: {id: 1, name: "test", group: "", description: "", creationDate: 1676993540,…} active: true creationDate: 1676993540 cronJob : "" description : "" executorClass : "Elements\\Bundle\\ProcessManagerBundle\\Executor\\PimcoreCommand" executorClassObject : null executorSettings : {values: {id: "1", name: "test", group: "", description: "", restrictToRoles: "0", callback: "",…},…} actions : [] loggers : [] values : {id: "1", name: "test", group: "", description: "", restrictToRoles: "0", callback: "",…} callback : "" command : "export-toolkit:export" commandOptions : "--config-name=\"Magento_Articledata\"" cronjob : "" defaultPreDefinedConfig : "" deleteAfterHours : "" description : "" group : "" id : "1" keepVersions : "" name : "test" restrictToRoles : "0" group : "" id : 1 keepVersions : null lastCronJobExecution : null modificationDate : 1676993540 name : "test" restrictToPermissions : null restrictToRoles : ",0," success : true

@ctippler
Copy link
Contributor

Hi,
the issue seems to occure when no callback window is defined. Could you please update to v4.1.2 - this should fix the issue.

Regards,
Christian

@MMierzynski
Copy link

@ctippler works well. Thanks for the fast action

@childhomie
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants