missing DB field fail_counter after the upgrade to 0.0.2

[RAYs3T]

After updating chaning events is no longer possible.

Seems like migrations did not run?

[dav_push] Fehler: transport web-push failed to deliver notification to subscription 3. error message: An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fail_counter' in 'field list'
	PUT /remote.php/dav/calendars/RAYs3T/company-events/ccdfec50-797d-48db-b1f3-ee21eaa74f73.ics
	von 2a04:4540:6a21:550:7d0f:20e4:56b:7bcd von RAYs3T um 12 Feb 2025, 12:55:10

[webdav] Fehler: An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'fail_counter' in 'field list'
	PUT /remote.php/dav/calendars/RAYs3T/company-events/ccdfec50-797d-48db-b1f3-ee21eaa74f73.ics
	von 2a04:4540:6a21:550:7d0f:20e4:56b:7bcd von RAYs3T um 12 Feb 2025, 12:55:10

• Running occ db:add-missing-columns has no effect.
• Re installing the app has also no effect.

For now I've added the field manually, which fixed the issue.

ALTER TABLE `oc_dav_push_subscriptions`
	ADD COLUMN `fail_counter` BIGINT(20) NOT NULL AFTER `expiration_timestamp`;

[JonathanTreffler]

How did you update ? Using the App Store ? Or manually (from github) ? Are there any error messages in the nextcloud.log or error.log from around the time of the update ?
Because that column should have been created by migration Version002Date20250119180000, which is a really simple migration that should run without any problems.

Please post which migrations ran on your instance using:

SELECT * FROM oc_migrations WHERE app = "dav_push";`

Please also post which database software you use, as this app was tested on mysql/mariadb, maybe the problem only happens on postgres or sqlite.

[RAYs3T]

Installation (and update) was done via the UI/Web App-Store.
Errors show was only the listed above and nothing else related to the app.

I'am actually unable to reproduce this issue. After validation on a copy restored from backup, everything is working fine.

So whatever went wrong on the update there, seems to be no general issue.

Database is mariaDB