LogBackend: server responded with status code: 504 - Resolution?

We are using openbalena along with balenaOS 2.88.4 and supervisor 12.11.0. I first noticed an issue when devices no longer report being online, “IS ONLINE” when running balena-cli devices always shows as “false” despite the devices being online. When I checked out the supervisor container logs to look for clues, I found the errors below relating to LogBackend. I’ve noticed other users have this same problem but can’t seem to find a resolution anywhere - does anyone know what might be causing it?

[debug]   Spawning journald with: chroot  /mnt/root journalctl -a -S 2021-12-20 03:54:33 -o json CONTAINER_ID_FULL=3c573858628819a4ec0005716da9d08e6836936734235dcd5145220bdd5f44a7
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[api]     GET /v1/healthy 200 - 13.162 ms
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[api]     GET /v1/healthy 200 - 7.779 ms
[debug]   Attempting container log timestamp flush...
[debug]   Container log timestamp flush complete
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[api]     GET /v1/healthy 200 - 7.127 ms
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[debug]   Attempting container log timestamp flush...
[debug]   Container log timestamp flush complete
[api]     GET /v1/healthy 200 - 5.961 ms
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[error]   LogBackend: server responded with status code: 504
[info]    Healthcheck failure - At least ONE of the following conditions must be true:
[info]          - No applyInProgress      ? false
[info]          - fetchesInProgress       ? false
[info]          - cycleTimeWithinInterval ? false
[error]   Healthcheck failed