I was able to create a Temporal Schedule using a non existing Workflow and non-existing task-queue. It appears to have created a task and a workflow. There are, obviously, no workers but that workflow is executed.
This looks like a bug.
This is by design. You don’t want to fail scheduling workflows if your workers are down.
1 Like
I guess I was expecting it to give a warning or error stating the task-queue or workflow does not exist. Especially, when we are using the cli to schedule workflow execution
Temporal doesn’t require registration of task queues. They are created on demand, which greatly simplifies their maintenance. But I agree that in some situations rejecting workflow start would be nice. The long-term solution would be using Nexus to hide workflow internals like task queue names.