BoldSign Blogs

  Advanced job scheduling with Quartz.NET is the practice of using a dedicated, persistent scheduler to run time-based, recurring, and distributed jobs reliably across your .NET applications. Quartz.NET gives you a scheduler, jobs, triggers, and durable job stores so your schedules survive restarts, scale across multiple instances, and avoid missed or duplicate executions. ( quartz-scheduler.net ) If you’re an ASP.NET Core or .NET back-end developer or architect building nightly syncs, billing cycles, report generation, or any recurring background work, Quartz.NET solves the problems that Timer, Task.Delay, and cron scripts eventually hit in production: clock drift, app restarts, multi-instance conflicts, and lack of observability. In this guide, you’ll learn how Quartz.NET works under the hood, how to integrate it into ASP.NET Core, how to handle misfires and clustering, and what patterns you need to avoid missed runs, duplicate jobs, and scheduler overload in real production syst...

  Running a nonprofit organization comes with a strong responsibility to remain transparent, legally compliant, and accountable. At the heart of this responsibility is nonprofit governance. Every major decision, from approving budgets to signing policies, must be reviewed and approved by the board. However, managing board approvals is not always simple. Board members are often busy, located in different places, or dependent on manual approval methods. These challenges can delay decisions, increase administrative effort, and slow down the organization’s ability to act. In this blog, see how nonprofits can manage nonprofit board approvals more efficiently using digital workflows, and how an electronic signature solution like BoldSign helps simplify the entire process. What is nonprofit board governance A nonprofit’s governance structure defines how a nonprofit’s board oversees decision making to ensure the organization stays ethical, legally compliant, transparent, and aligned with ...

  Long-running tasks in ASP.NET Core like generating reports, processing files, or calling slow third-party services shouldn’t run inside controller actions. Keeping an HTTP request open while you do heavy work causes real problems: Timeouts (clients, reverse proxies, load balancers) Lower throughput (requests occupy resources longer) Unreliable execution (deployments/restarts kill in-flight work) Retry amplification (timeouts trigger retries → more load → more timeouts) A better pattern is simple: Accept the request quickly Enqueue the work Return 202 Accepted with a job ID Process the work in the background Let the client check status (or receive a webhook callback) What counts as a “long-running task” in ASP.NET Core A “long-running task” is any work that’s long enough to risk timeouts, tie up resources, or get interrupted by restarts. Common examples: Bulk email sending PDF/Excel report generation File post-processing (virus scan, thumbnails, transcodes) Video/image processing ...