https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • s
    And can I run same cron in multiple regions at the same time?
  • w
    not natively but there's a few ways to do it: * Healtchecks - you can run these from multiple regions, simply have them hit your Worker * Durable Objects - create them in what regions you want then call them in your cron Worker
  • s
    thanks again
  • s
    this is what I do but our sourcemaps have been pretty hit or miss. lots of time there is no context or it's incorrect 😦
  • w
    I'd look at your code honestly, it's been working great for me both in personal and work projects
  • s
    I think it's mostly when manually doing 
    sentry.captureException
    and also sometimes when there is an error deep in a library then there is no context
  • s
    actually I have a great example from yesterday because it is from the same webhook route
  • s
    missing stack trace (only shows the library code)

    https://cdn.discordapp.com/attachments/779390076219686943/1112295110055563344/image.pngâ–¾

  • s
    actually I don't want to show screenshot of the second one but its code in the same route itself that manually calls 
    throw new Error
    and the full stack trace is there
  • s
    the other issue I get is with errors sometimes not de-duplicating themselves. is this something I need to config differently?

    https://cdn.discordapp.com/attachments/779390076219686943/1112295609043533945/image.pngâ–¾

  • s
    also with some DO errors I sometimes get errors like this with zero stack trace. I think 
    itty-durable
    is probably losing the context somehow since they use a proxy object or something. this one does get de-duplicated though

    https://cdn.discordapp.com/attachments/779390076219686943/1112296074313478215/image.pngâ–¾

  • p
    guys all my workers just got about 200-2k requests all at 9:00 together
  • p
    what kind of wierd issue is this
  • p
    by all i mean all worker service deployed in my account
  • s
    Yeah, perhaps Workers for Platforms is the direction I need to go then—with a worker per customer. I'll look into that. Thanks 🙂
  • i
    What's the best way to store logs from workers , current options seems to all require either R2 or an external destination to store them, with each storing costing a R2 write
  • w
    logpush is the way and r2 is one option. You can also use others though like Backblaze which would be cheaper They're batched and sampled (depending on your option) so you don't pay per request but yeah, it will likely cost a write at wherever you store
  • i
    I have no enterprise for logpush tho

    https://cdn.discordapp.com/attachments/779390076219686943/1112399318733815808/image.pngâ–¾

  • i
    Ahh there is workers trace events logpush
  • w
    Workers Logpush doesn't require ENT
  • w
    just Workers Paid
  • i
  • s
    My worker is timing out in 1m 20s, it used to work fine earlier 😦
  • s
    Now I'm getting 502
  • s
    My current plan is Paid + Unbound but this unlimited duration is confusing, it's mentioned 15m in some places (for schedule triggers only) and then it's mentioned as uncapped in some places. I need to understand if worker can run for longer duration (earlier it used to work fine, but I don't exactly remember) Would really appreciate any help @Walshy | Pages my live production app is facing this issue

    https://cdn.discordapp.com/attachments/779390076219686943/1112403304723525762/image.pngâ–¾

    https://cdn.discordapp.com/attachments/779390076219686943/1112403305017122856/image.pngâ–¾

    https://cdn.discordapp.com/attachments/779390076219686943/1112403305247821824/image.pngâ–¾

  • w
    It ca run for a long time
  • w
    It can only use 30 seconds of CPU time (or 15 min in cron triggers)
  • w
    the wall clock time is what is "unlimited", it can run for as long as it can
  • w
    the limit is on the CPU time just like Bundled
  • w
    agree the way we word/represent it is confusing
1...25052506250725082509Latest