https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • j
    Trace was renamed to tail. They’re the same thing, with trace still supported for backward compatibility
  • u
    Understood thank you
  • d
    I thought uncaught exceptions in workers triggers a status to fail?

    https://cdn.discordapp.com/attachments/779390076219686943/1111521681480101998/image.png▾

  • d
    Basically I'm intercepting the response being returned, but before it's returned, going to a 
    ctx.waitUntil
    and throwing an error based on that 
    response.ok
    . That way I can have my worker status code in the cloudflare dashboard match the actual http response (easier for visibility).
  • d
    As you can see in the screenshot, it's picking up that Error I'm throwing, but in the top left, it still says 
    OK
  • u
    If the worker sends a response the status will be ok. Only failing to send a response will it not be ok
  • d
    even if there's an uncaught error in 
    waitUntil
    ?
  • d
    I thought status is supposed to be error if anywhere (before or in 
    waitUntil
    ) there's a uncaught exception
  • h
    What would cause ``API Request failed: We were unable to enable Workers Unbound on your account. Please try again.``?
  • h
    Copy code
    Subscribe to this product to proceed. Your account does not have access to this product.
  • h

    https://cdn.discordapp.com/attachments/779390076219686943/1111573894885806110/image.png▾

  • b
    As workers sit on the edge and happen before page rules, has anyone figured out an efficient way of still utilising cloudflare url normalisation? Or is this impossible?
  • k
    Page Rules apply to Workers
  • k

    https://cdn.discordapp.com/attachments/779390076219686943/1111585919171039242/image.png▾

  • k
    Workers is at the bottom, not before Page Rules
  • b
    Oh thanks Kian, my mistake!
  • w
    What's your account ID?
  • m
    I have hit the same issue. I don't think "Please enable cookies" is important here. It is an element on the error page. If the page is rendered in a browser with cookie enabled it will not be displayed. With saying that, I don't know what is the real problem that has caused the error.
  • k
    That post is more than a year old - 1101 means your Worker code threw an uncaught exception.
  • h
    where can I find this?
  • w
  • h
    DM'd
  • w
    Thanks, I'll escalate in a bit when I start work
  • h
    Thanks!
  • l
    Any decent alternatives to Fauna DB for Workers?
  • b
    anyone know why I cant seem to use 2 
    /
    on a worker route? I have even added url sanitisation to remove duplicates but I get strange errors. I am just trying to return the request
  • p
    Why won't cloudflare serve my images? i've deployed on vercel and everything works fine but when I connect it with cloudflare with their nameservers and point my domain to my vercel deployment, my images don't show.
  • r
    How can I deploy a node.js-based application onto worker?
  • r
    It runs on my computer well
  • n
1...249624972498...2509Latest