It appears to be a bug? This happened multiple times. When I first deployed a new Workflow to an environment, the code invocation would result in 
Error: (workflow.not_found) Provided Workflow does not exist. Upon the second redeployment, it would work correctly.Error: (workflow.not_found) Provided Workflow does not exist
BwaitForEvent fails due to a timeout exception, the step is retried as expected.
PWorkflow V2: Error processing batch 5 {
"message": "Aborting engine: Grace period complete",
"error": {
"remote": true,
"durableObjectReset": true
},
O10001 as earlier.This instance experienced an internal error which prevented it from running. If this is persistent, please contact support: https://cfl.re/3WgEyrHqueued state and will never run.P
M
D
A
SPO
C
--remote for it work.--remote also makes my workflow to run remotely as well. Ideally, I'd like to run workflows locally while still being able to have certs work.MMCM
R
TMO
R
, i am running bullmq for now buts its failing, otherwise i have to scale that or run kafka until this is resolved
N
T
Error: (workflow.not_found) Provided Workflow does not exist
IMMTMM
T
7
hi all - wondering if anyone has any resources to help me get vitest working since adding 
[[workflows]] to my toml file?isolatedStorage otherwise it was complaining about not being able to find my imported Workflow class to bind.workerd/jsg/util.c++:320: error: e = kj/table.c++:49: failed: inserted row already exists in table
7singleWorkfer: true got it working, so it must be that the workflows each spin up their own worker, and try to initialize something for each test?DSNMDA
M
MAcreateBatch to do 100 at a time within each of the initial 31. The total amount gets queued up very quickly. The graph above is the steps processing inside those from my understanding. Mexport class SimpleWorkflow extends WorkflowEntrypoint<
Env,
SimpleWorkflowPayload
> {
async run(event: WorkflowEvent<SimpleWorkflowPayload>, step: WorkflowStep) {
console.log("Simple workflow started", event.payload);
await step.do("testing timeout", async () => {
console.log(`Initializing test: ${event.payload.name}`);
const eventResponse = await step.waitForEvent("waiting for event", {
type: "test",
timeout: 10000,
});
console.log("Test event received", eventResponse);
return { status: "initialized" };
});
console.log("workflow complete");
}
}waitForEventWorkflow V2: Error processing batch 5 {
"message": "Aborting engine: Grace period complete",
"error": {
"remote": true,
"durableObjectReset": true
},10001This instance experienced an internal error which prevented it from running. If this is persistent, please contact support: https://cfl.re/3WgEyrHqueued--remote--remotename = "docpad-session-init"
main = "src/index.ts"
compatibility_date = "2024-10-22"
compatibility_flags = ["nodejs_compat"]
[[workflows]]
binding = "DOCPAD_SESSION_INIT"
name = "docpad-session-init"
class_name = "DocpadSessionInit"[[workflows]]isolatedStoragesingleWorkfer: trueconst db = getDB(this.env);// inside the run() method
const db: TypeOfYourDB | undefined// elsewhere, as a helper - e.g. on the Workflow class
async function getDB(db, this.env) {
if (!db) {
db = // create a new connection
}
return db
}createBatchimport { defineWorkersConfig } from '@cloudflare/vitest-pool-workers/config';
export default defineWorkersConfig({
test: {
poolOptions: {
workers: {
isolatedStorage: false,
wrangler: { configPath: './wrangler.toml' },
},
poolMatchGlobs: [],
},
maxConcurrency: 1,
},
})import { createExecutionContext } from "cloudflare:test";
import { describe, it, expect } from "vitest";
describe("test", () => {
it('test', () => {
// referencing something from cloudflare:test
const ctx = createExecutionContext()
expect(2).toBe(2)
})
})