Yuri van Oers

If it's for debugging purposes, would it be a solution to put the object ID in the `displayname` instead of the `name`? `displayname` accepts just about anything.

> Yes @yvanoers this is a breaking change, this is why this will be published in 4.x, you can not upgrade in place but it only requires of a rolling...

Ah yes, great! And here's a PR to improve some of the text: #980 :)

Nope, at least, not publicly. Feel free to do so and submit a pull request, if you think it is useful.

This is a similar to what is discussed in #823. Because #823 was initially a misunderstanding of what Dkron uses as expressions, and this issue is an actual feature request...

It seems to me like dkron is being used somewhat like a task queue processor in this scenario. That could actually be very useful, but it is not the intended...

IIRC, the main reason to do it the way it is now was to keep in line with how react-admin does things, and not introduce a secondary storage mechanism. I'm...

Could you elaborate on when and how you run into this?

What benefit do you get from using a gRPC client to get Dkron to do stuff? In other words: why aren't you using the REST API?

You're a bit stingy with information, so it's not quite clear if this is a support request or a feature request. A few thoughts: \- The shell executor was recently...