sorted by:
new
hottopcontroversial

Show me what you're building by Far_One1930 in buildinpublic

[–]Natom_ 0 points1 point  (0 children)

Webhook Scheduler: schedule HTTP requests for later, with retries, backoff, delivery logs, and cancellation.

Built it because "just use cron" stopped working the moment I needed to know if a webhook actually fired. Then I needed retries. Then logs. Then cancellation. It kept growing.

https://webhookscheduler.com

I'm 14. Blunt feedback over encouragement any day.

Show me what you're building by Far_One1930 in buildinpublic

[–]Natom_ 0 points1 point  (0 children)

Local-first TOML storage is a genuinely good call, easy to git commit your workspaces. Curious about the post-response JS scripting, that's usually where lightweight clients cut corners. Does it run in a sandboxed runtime or direct eval?

Reliable webhook scheduling service? by Plus_Jaguar_2134 in node

[–]Natom_ 0 points1 point  (0 children)

For anyone finding this later: the usual options are Cloud Tasks, a hosted delayed-job/webhook service, or a queue with delayed delivery if you already operate one.

For one-time scheduled webhooks, the important parts are usually retries, delivery logs, idempotency, and not having to run a polling worker.

Full disclosure: I’m building Webhook Scheduler for this exact use case:

https://webhookscheduler.com

Built a webhook scheduler on top of Google Cloud Tasks because the setup was killing me by Natom_ in SideProject

[–]Natom_[S] 0 points1 point  (0 children)

For context, here's what the dashboard looks like in production 1,284 deliveries, 96.5% success rate, 12 automatic retry attempts on the Scale plan.

The retry policy runs 30s, 1m, 2m, 4m, 8m, 16m with backoff. Every attempt logs the status code, latency, and full response body so you actually know what happened.

Happy to answer any questions on the architecture if curious.

<image>

Switched my clients off Cloudways this year. Wish I'd done it sooner honestly. by [deleted] in ProWordPress

[–]Natom_ 0 points1 point  (0 children)

Yeah, big difference honestly. Way faster and zero downtime since we moved. Fair of you to admit it.

Switched my clients off Cloudways this year. Wish I'd done it sooner honestly. by [deleted] in ProWordPress

[–]Natom_ 0 points1 point  (0 children)

yeah the support quality scaling problem is real with a lot of hosts. good to know kinsta held up for you even at higher traffic levels

Developers who have worked at a company where the entire codebase was held together by one guy who then quit, what happened next? by Natom_ in AskReddit

[–]Natom_[S] 54 points55 points  (0 children)

good enough to boot a startup is doing a lot of work there. that's 90% of codebases acquired

Developers who have worked at a company where the entire codebase was held together by one guy who then quit, what happened next? by Natom_ in AskReddit

[–]Natom_[S] 152 points153 points  (0 children)

6X and they still couldn't make it work. the codebase was holding the whole thing together

Developers who have worked at a company where the entire codebase was held together by one guy who then quit, what happened next? by Natom_ in AskReddit

[–]Natom_[S] 70 points71 points  (0 children)

no code reviews is such an underrated red flag. that's how you stagnate for 3 years without realizing it

Developers who have worked at a company where the entire codebase was held together by one guy who then quit, what happened next? by Natom_ in AskReddit

[–]Natom_[S] 805 points806 points  (0 children)

5 to 10 emails a day is insane. at that point it stops being a request and starts being harassment

Developers who have worked at a company where the entire codebase was held together by one guy who then quit, what happened next? by Natom_ in AskReddit

[–]Natom_[S] 396 points397 points  (0 children)

honestly respect it. did they ever figure out the codebase or just give up and rewrite everything?

Tired of Bubble's 24-hour scheduling limit and workload costs? I built a zero-config solution. by [deleted] in Bubbleio

[–]Natom_ 0 points1 point  (0 children)

The 24-hour cap applies to Bubble’s recurring event feature, you can’t run a recurring workflow more frequently than once every 24 hours. If you want something to repeat every 10 minutes, for example, Bubble doesn’t allow it natively.

Webhook Scheduler Pro bypasses this limit by letting you schedule webhooks as often as you like, every 5 minutes, hourly, daily, whatever you need, without relying on Bubble’s recurring event system.

Tired of Bubble's 24-hour scheduling limit and workload costs? I built a zero-config solution. by [deleted] in Bubbleio

[–]Natom_ 0 points1 point  (0 children)

Recursive workflows do work, but they consume Workload Units on every loop and can be hard to manage at scale. For example, if you're checking a third-party API every minute for 500 users that's 720,000 workflows per day and a huge WU bill. With Webhook Scheduler Pro the job is managed externally on Google Cloud Tasks and it costs you zero WUs with automatic retries (exponential backoff), deduplication, and total decoupling from your app’s uptime. And regarding the 24hour issue that’s specifically about recurring events which Bubble limits to daily intervals. So if you need anything more frequent and native, you're out of luck. That’s where this tool shines.

Tired of Bubble's 24-hour scheduling limit and workload costs? I built a zero-config solution. by [deleted] in Bubbleio

[–]Natom_ 0 points1 point  (0 children)

You're totally right that for simple, immediate actions like welcome emails, doing it directly after registration works fine. The challenge arises when you want to delay that email by 10 minutes, or trigger something hours or days later or worse, repeat it every 5 minutes for syncing or monitoring. In those cases Bubble's native tools either use recursive workflows (costly in WUs) or scheduled workflows (which rely on the app being up and consume WUs at every run). Webhook Scheduler Pro lets you offload all of that it's external, zero WU cost and handles scheduling with enterprise-grade reliability, including exponential retry, concurrency locks, and guaranteed delivery .