Cloudflare Developers•2w ago

Limits for paid workers

I'm sorry beforehand if this question is 'stupid' but I am a bit confused, the worker has 3 days, is it consuming more than the covered by the paid workers?

5 Replies

Walshy•2w ago

https://developers.cloudflare.com/workers/platform/pricing/ You are over the 10 mil included requests yes, so you currently have a $0.6 overage for that You're below the included CPU time so good there https://developers.cloudflare.com/workers/observability/logs/workers-logs/#pricing as for logs, you're below the included 20 mil but close

布鲁诺普雷托OP•2w ago

Is it possible to only have the console.logs running the wrangler dev ? Also, I'd love to have some notes regarding proper way of configuration for the wrangler.jsonc file so I can use the resources cloudflare offers the 'proper' way/ efficient Out of the top of my mind, supposedly I would need to have a special function for logs where it checks if I'm in dev or production env, but I'm not sure how to accomplish this. Thanks for your time ❤️ In the most recent workers project the one in the sc I have the following wrangler.jsonc

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "####",
    "main": "src/index.js",
    "compatibility_date": "2025-03-17",
    "account_id": "#######",
    "observability": {
        "enabled": true
    },
    "vars": {
        "ENVIRONMENT": "dev"
    },
    "env": {
        "staging": {
            "workers_dev": true,
            "vars": {
                "ENVIRONMENT": "staging"
            }
        },
        "production": {
            "vars": {
                "ENVIRONMENT": "production"
            }
        }
    },
    "triggers": {
        "crons": [
            "45 * * * *"
        ]
    },
    "d1_databases": [
        {
            "binding": "DB",
            "database_name": "#####",
            "database_id": "#####3"
        }
    ],
    "queues": {
        "consumers": [
            {
                "queue": "####",
                "retry_delay": 60
            }
        ],
        "producers": [
            {
                "queue": "#",
                "binding": "TUQ",
                "delivery_delay": 30
            }
        ]
    }
}

{
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "####",
    "main": "src/index.js",
    "compatibility_date": "2025-03-17",
    "account_id": "#######",
    "observability": {
        "enabled": true
    },
    "vars": {
        "ENVIRONMENT": "dev"
    },
    "env": {
        "staging": {
            "workers_dev": true,
            "vars": {
                "ENVIRONMENT": "staging"
            }
        },
        "production": {
            "vars": {
                "ENVIRONMENT": "production"
            }
        }
    },
    "triggers": {
        "crons": [
            "45 * * * *"
        ]
    },
    "d1_databases": [
        {
            "binding": "DB",
            "database_name": "#####",
            "database_id": "#####3"
        }
    ],
    "queues": {
        "consumers": [
            {
                "queue": "####",
                "retry_delay": 60
            }
        ],
        "producers": [
            {
                "queue": "#",
                "binding": "TUQ",
                "delivery_delay": 30
            }
        ]
    }
}

However I'm not sure what is the appropriate way to handle environments I usually just do production tests, bad habit, but I cant seem to figure out the proper way for the dev environment

布鲁诺普雷托OP•2w ago

This is not good right ? @Walshy

布鲁诺普雷托OP•2w ago

I forgot to re-upload the version for production, and now I think I will have a huge bill 😦

1984 Ford Laser•2w ago

Yeahhh rows written are $1 per million after the first 50mil...

Gaming

Programming

Limits for paid workers

Did you find this page helpful?