You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARN [autokuma::sync] Encountered error during sync: Server responded with an error: insert into monitor_notification (monitor_id, notification_id) values (97, '1') - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed
In reality monitor is created in uptime kuma, but autokuma keeps on recreating it in indefinite loop.
Scenario in which this happens - I try to redeploy uptime kuma + autokuma from code, since not all objects can be defined in code (in this case notifications) some objects are missing initially and this causes the creation loop.
The text was updated successfully, but these errors were encountered:
I've already mentioned this in some other issue but this is a uptime kuma bug. There's basically nothing I can do about this, uptime kuma does not report the id of the newly created monitor in this failure case so there's no way for autokuma to know about the new monitor and frankly uptime kuma should probably clean up any half created monitors anyway.
Btw. since you're already on master, you can create notifications (and tags and docker_hosts) using autokuma, see #81
I've already mentioned this in some other issue but this is a uptime kuma bug. There's basically nothing I can do about this, uptime kuma does not report the id of the newly created monitor in this failure case so there's no way for autokuma to know about the new monitor and frankly uptime kuma should probably clean up any half created monitors anyway.
Btw. since you're already on master, you can create notifications (and tags and docker_hosts) using autokuma, see #81
error:
In reality monitor is created in uptime kuma, but autokuma keeps on recreating it in indefinite loop.
monitor example:
Scenario in which this happens - I try to redeploy uptime kuma + autokuma from code, since not all objects can be defined in code (in this case notifications) some objects are missing initially and this causes the creation loop.
The text was updated successfully, but these errors were encountered: