workflows: this.name is not set when trying to run inside an alarm

[jcheese1]

Describe the bug
A clear and concise description of what the bug is.

@callable()
async testSchedule() {
  this.schedule("0 0 * * *", "startWorkflow", {});
}

async startWorkflow() {
  const workflowId = await this.runWorkflow("PROCESSING_WORKFLOW", {});
  ///
}

The above code will result in:

error executing callback "startWorkflow" Error: Attempting to read .name on TestAgent before it was set. The name can be set by explicitly calling .setName(name) on the stub, or by using routePartyKitRequest(). This is a known issue and will be fixed soon. Follow https://github.com/cloudflare/workerd/issues/2240 for more updates.

I attempted a temp fix on the partyserver level here: cloudflare/partykit#331

Expected behavior
The workflow executes even in a scheduled/alarm function on cold wake

Version:
0.4.1

[threepointone]

I've been trying to keep partyserver free from touching storage but tbh seems necessary now. I'll have a look at this soon, thanks.

[jcheese1]

i mean, if you really dont want to, something like this will work in the meantime for me:

const agentName = this.state.name;

const instance = await this.env.PROCESSING_WORKFLOW.create({
  id,
  params: {
    __agentName: agentName,
    __agentBinding: "TestAgent",
    __workflowName: "PROCESSING_WORKFLOW",
  },
});

// Manually track (replicates what this.runWorkflow does internally)
this.sql`
  INSERT INTO cf_agents_workflows (id, workflow_id, workflow_name, status)
  VALUES (${crypto.randomUUID()}, ${instance.id}, ${"PROCESSING_WORKFLOW"}, ${"queued"})
`;

[threepointone]

I will fix this next week