Cloudflare

Also, this also affects the `staging` environment and the default one (while other projects seem to work fine)

Hey would anybody have any insight into what would be causing my context object to be empty when I start a request?
I'm currently trying to invoke context.waitUntil but it is undefined...

It's in astro that this isn't working

```
import { getRuntime } from "@astrojs/cloudflare/runtime";

export async function onRequest ({ locals, request }, next) {
    const runtime = getRuntime(request)
    const cacheUrl = new URL(request.url);
    const cacheKey = new Request(cacheUrl.toString(), request);
    const cache = caches.default
    let response = await cache.match(cacheKey)
    if (response) return response
    locals.accountConfig = accountConfig
    response = await next()
    response.headers.append("Cache-Control", "s-maxage=60");
    runtime.waitUntil(cache.put(cacheKey, response.clone()))
    return response
};
```

got a code snippet

Works now! Thank you, <@1052249953570918430>  and <@312617227490951168> !

One quick question though: It seems like log messages from a queue consumer are only delivered when the consumer terminates, is that expected behaviour?

In other words, they are not live streaming but I get a bunch of log messages once the consumer function is done

Does anyone else see cron jobs not being triggered?

It seems to be fine for me what schedule is your cron job on and is it just not showing in past cron events so you assume it didnt run or can you verify that it didnt actually run via other means?

Yeah it's supposed to modify KV values. It runs every 5 minutes, and it worked fine earlier today

ah! it worked at 45'. Between 05' and 45' it should have run though :/

Oh nice 🙂 if it happens again feel free to post in here and we can ping the team there has been a few people reporting issues with cron triggers

Hi <@684048302232305757> , you told me to message you on the Discord here regarding https://github.com/eidam/cf-workers-status-page/issues/129

Or anyone else who can help 🙂 The issue is about suddenly getting Cloudflare usage errors when we haven't changed anything in a few weeks

As Rob said in his message on that github issue. Can we get the account id and kv namespace id so they can look into it

Account ID: 4b89b0167ca190dd7c92e18a4d1737f5
KV ID: 14ad4847223146fe8b0a95d88f8ff064

Just to make sure you did change the cron trigger to only run every 2 minutes like that repo says?

i haven't changed the cron in a few weeks

If you go to your CF dashboard and go to the worker then click into logs and then the "Past Cron Events" section can you screenshot the list of events


https://cdn.discordapp.com/attachments/779390076219686943/1108803791161131121/Screen_Shot_2023-05-18_at_1.10.33_PM.png

it's still running which makes me think it's a reporting issue

In the email I got: "Requests to put values from the Workers KV API will return 429 errors and put operations within a Worker will fail until the limit resets at 2023-05-19 at 00:00:00 UTC."

<@1052249953570918430> looks like another double trigger cron issue ^^