[BUG/QUESTION] Job/Workflow name requires lowercase?

[indrif]

Describe the issue

I am evaluating Hatchet a little more for our use case and created a simple example looking something like this:

const name = "HatchetTestJob";
const wf = hatchetClient.task({
  name,
  fn: async () => console.log('Hello from hatchet task!'),
});
const worker = await hatchetClient.worker('worker1', {
  workflows: [wf],
});
await worker.start();

When running this I can see in the dashboard that the workflow name is in all lowercase:

However when I try to run the workflow:

const workflow = hatchetClient.workflow({
  name,
});
const a = await workflow.runNoWait();

I get the following error:

🪓 53950 | 01/21/26, 02:05:36 PM  [ERROR/Admin] Error: /WorkflowService/TriggerWorkflow INVALID_ARGUMENT: could not trigger workflow: rpc error: code = InvalidArgument desc = workflow names not found: HatchetTestJob undefined

It is complaining about workflow not found. I then chaned to this:

const workflow = hatchetClient.workflow({
  name: name.toLowerCase(),
});
const a = await workflow.runNoWait();

And this works. Is this how it is supposed to work? Is it a requirement that is not documented? If so, then hatchet should probably normalize the job name in every place, not only when creating.

Are there any other limitations to how names can be used? Special or reserver characters? Is it possible to allow it to use both UPPERCASE and lowercase letters?

Environment

• SDK: ts 1.10.5
• Engine: cloud

[grutt]

Hi @indrif thanks for the report, this is definitely a bug and I'm surprised we haven't seen this before. We are normalizing the name but perhaps there is some inconsistency between the workflow and task stub factories here... I'll look into this

I'm curious is there a reason you're using workflow instead of task?

const workflow = hatchetClient.task({
  name,
});
const a = await workflow.runNoWait();

[indrif]

Hi @grutt !

Nice to hear, thanks. Any other clarifications regarding naming conventions that we need to be aware of (reserved chars etc maybe)?

Also, regarding workflow vs task: that is an interesting question and one where I do not understand what is the difference between task vs workflow.

For some reason I thought that workflow was the one to use for stubs (since task takes the actual function to invoke as a param) but I see now that task.fn is optional. It is not very clear to me which one to use from reading the documentation, but maybe I have missed something?