Open retroph opened 6 years ago
For Twitter those are less of an issue, they just result in "status is a duplicate" errors.
Root cause: DB triggers (on run creation) are only guaranteed to be run at least once, and should be idempotent.
For Twitter those are less of an issue, they just result in "status is a duplicate" errors.
Root cause: DB triggers (on run creation) are only guaranteed to be run at least once, and should be idempotent.