I can’t tell you the details since I don’t know them. But there is a hardware watchdog, which I guess is an IC / part of the sillicon which needs to be periodically “reloaded” in order not to reset the MCU (default 3 seconds if I recall correctly). This is done by openat itself if you don’t block, but when you process large amount of data you might get close to the expire time. So either you can try to set the expire time to a longer value or periodically reset it while processing data. Note that this while block the whole execution of the “application” context and the application might become less responsive (or lock it up at all, so don’t start processing immediately, but always wait for a startup delay, to at least be able to send an AT+WOPEN=0).
The application wachtdog is a watchdog implemented by openat, it can simply be (temporarily) disabled.
Alternatively you could (perhaps?) put the large work in a lower priority task and call adl_ctxSleep every now and then. But I don’t have much experience with the multiple task feature provided.