When having multiple instances, if the instance itself is responsible for the scheduled execution, all instances will execute at roughly the same time and lead to duplicated work and might lead to multiple reports/emails/notifications.

NET Core, so it might run on any platform, leading me to go away from any OS-specific solutions right from the get-go.Īdditionally, it feels like it's a monolith for the time being, but if you need to be fault-tolerant and scale, you'd like to run at least a couple of instances. I've glanced over the comments but I cannot seemingly find a solution I personally would be comfortable with in regards to scalable cloud deployments. Any advice on this would be more than welcome!Įdit: Thanks to all for your advice! I ended up creating a Scheduled Task with Invoke-WebRequest to call both endpoints at the desired time. I'm pretty sure there must be a very simple way to achieve this, I just haven't found it.

I've seen HangFire, but people here don't like the idea of setting up a database for that. I would note that I don't have access to IIS, I always need my manager to make those configs and after bothering a lot without success I'm now looking for other solutions. I've tried multiple configurations on IIS for this but don't seem to work. But the next day, the email report won't trigger at all. I know this because if I trigger manually the email report, the next task that is triggered 3 hours later fires up. It seems that IIS is sort of sleeping the background service after some time passed. But the thing is, it works as expected in development (my machine), but it doesn't once it is published in IIS. Then I created a background service within the same API that triggers both needed actions (Please let me know if this is considered bad practice). I made a simple Web Api for this and ended up with two endpoints that do what I need. Send that Inventory Listing to other API (customers API) Send an Inventory Report via Email every day at a certain time

Net core scheduled task