Silently rejecting jobs when the db is not connected

[Dam-Buty]

Hi,

I have a question that might point to a bug.

Recently i've been using PG-Boss in a set of CLI scripts, but was surprised to see that no jobs were created. It turned out that when writing the CLI wrapper I had made a mistake and forgotten to start() the PG Boss instance.

As a result, db.executeSQL would just fail silently on this line , and the job creation would return null.

• it seems strange that the library would not throw an error in that case. I don't see any scenario where that would be expected behaviour.
• additionally it is pretty frustrating to receive a null jobId with no indication of what went wrong. Would you consider adding a helper function to investigate what prevents a job from being created ? (be it from singleton, throttling, or in this case an unopened DB handler)

Thanks and have a great day :v:

[wflanagan]

I had this problem.. the pooler can make the connection go away, and this is the result.