Sorry you encountered issues after the v1.5 upgrade. Accurate, transactionally safe, index backed uniqueness can cause issues with custom unique configurations.
We don’t have an official backport/support policy, but in general, once a new minor version is released we stop applying smaller bugfixes to older versions. If it’s a critical bug then we’ll backport, as we did for the issues in v1.5.4, but not for edge cases or smaller bugs.
The issue you encountered was considered an edge case that would only happen for certain unique configurations (most likely configurations that don’t actually prevent uniqueness). This is related to a support issue posted yesterday: Oban jobs stuck at "scheduled" and then "available" if I move them there manually - #4 by sorentwo
The best fix for this issue is to ensure that if you’re going to include executing, you list all incomplete states:
states: ~w(available scheduled executing retryable)a
Remember, uniqueness applies on insert only. Jobs are always inserted as available or scheduled, so a unique config without those states won’t prevent any inserts, it will just cause processing issues later on.
