Optimistic lock for Scheduling can break in certain databases

Description

I think.

We read the next_execution timestamp and then update matching on that it it can't find a match.

We should use a version long.

Environment

None

Status

Assignee

Nick Menere

Reporter

Nick Menere

Links

0

Fix versions

Priority

Configure