Apparent watchdog resets during/just after iridium transmission

[lauralindzey]

I want to look into what could be causing these resets. Here's what I've observed so far:

1. During the Arctic Pisces light calibration, microSWIFT203 reset itself 2x. When we pulled the logs, they showed:

Hello World!
microSWIFT 203.
Firmware major version 2, minor version 8.
Sample window 20
04/26/26 19:30:00: RTC Initialization successful.
[...]
04/26/26 19:58:17: Number of enqueued Waves messages: 1
04/26/26 19:58:17: Number of enqueued OBS message elements: 0
04/26/26 19:58:17: Number of enqueued Light message elements: 2
04/26/26 19:58:17: Attempting transmission of NEDWaves telemetry...
04/26/26 19:58:32: Iridium transmission unsuccessful. MO status: 32
04/26/26 19:58:32: RF switch set to Iridium port.
[end of file]

Hello World!
microSWIFT 203.
Firmware major version 2, minor version 8.
Sample window 5
04/26/26 22:45:00: RTC Initialization successful.
[...]
04/26/26 23:13:10: Number of enqueued Waves messages: 3
04/26/26 23:13:10: Number of enqueued OBS message elements: 0
04/26/26 23:13:10: Number of enqueued Light message elements: 5
04/26/26 23:13:10: Attempting transmission of NEDWaves telemetry...
04/26/26 23:13:32: Iridium transmission unsuccessful. MO status: 18
04/26/26 23:13:32: RF switch set to Iridium port.
[end of file]

2. While testing buoys, we noticed that 204 sent 3 messages in quick succession despite being configured for a 120 minute duty cycle.
   Our hypothesis is that it reset after a successful transmission, then immediately re-ran, then re-ran at the top of the hour as expected to start the duty cycle.