ratelimit and a workflow worker?
ratelimit[[unsafe.bindings]]
name = "RATE_LIMIT_MEASUREMENT_GUEST"
type = "ratelimit"
namespace_id = "1000"
simple = { limit = 3, period = 60 }export default class WorkflowsService extends WorkerEntrypoint<CloudflareEnv> {
// ...
async createWorkflow(payload: Params) {
// check if the user has exceeded the limit
const RATE_LIMITER = this.env.RATE_LIMIT_MEASUREMENT_GUEST;
const { success } = await RATE_LIMITER.limit({
key: payload.userIdOrIpAddress,
});
// success locally works as expected but on production I can x3/x4 the limit and still success=true (all sending the exact same
Jsmart placement)
M
M
M
森
J
森森
TTT
B
T
T
Z
(workflow.not_found) Provided Workflow does not exist in production.DD
S
O
S
env.WORKFLOW.get(id)? Error: instance.not_found). I've been unable to find a pattern for repro, except that it seems the codepath that invokes the workflow can successfully call get(id) later, even in a different instance of the worker; whereas some other codepath will always get instance.not_found. I'm using the same binding for the same worker with the same workflow id.
J
JOJJ
A
wrangler types expected to generate types for workflows defined in wrangler.toml
CC
restart()'ing an instance count to the 100 per 10 second liimit of the Maximum Workflow instance creation rate?M
DCDC
A
M
T
GGG
A
FAA
P
smartworkerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Missing deoptimization information for OptimizedJSFrame::Summarize.Getting User settings...
👋 You are logged in with an OAuth Token, associated with the email email@gmail.com.
┌──────────────────────────────────┬──────────────────────────────────┐
│ Account Name │ Account ID │
├──────────────────────────────────┼──────────────────────────────────┤
│ myemail@gmail.com's Account │ xbc │
└──────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- d1 (write)
- pages (write)
- zone (read)
- ssl_certs (write)
- ai (write)
- queues (write)
- pipelines (write)
- secrets_store (write)
- offline_access
🎢 Membership roles in "email@gmail.com's Account": Contact account super admin to change your permissions.
- Super Administrator - All Privileges
error: Recipe `deploy` failed on line 10 with exit code 1
`(workflow.not_found) Provided Workflow does not existenv.WORKFLOW.get(id)Error: instance.not_foundget(id)instance.not_foundwrangler typesKnown issue: Restarting a Workflow via the restart() method is not currently supported and will throw an exception (error).restart() // Something in one of these two steps causes the workflow to show outcome of "exception" and
// level of "error". What?
const { foo, bar } = await step.do("test", async () => {
const foo = "hello";
const bar = "world";
return {
foo,
bar,
};
});
await step.do("test", async () => {
return foo + bar;
});
// This will not cause an error...most the time...when it's the *only* step in the workflow.
await step.do("test", async () => {
return "foooo";
});