Background Recurring Jobs overuse red flags

I encountered a design practice in LOB (Line-of-Business) application where many scheduled Jobs are created.

We know clear-cut scenarios where Jobs are good fit - like sending e-mail notifications, but in this particular case, many parts of business logic is implemented to run in various intervals. In most cases, some internal data processing is done and outcome is saved back to the database, then some other Job picks it up, and so on.

In isolation each job kind of make sense – for example the processing is time consuming etc., but at one point I started to think:

• How many Jobs we can have until it gets out of hand,
• What could be unintended consequences of overusing this design,
• Is something fundamental missing in overall design or architecture?

Question is :

When Jobs could be considered inappropriate, are there any red flags to look for? Also, what architectures are there that might addresse this sheduled job approach?