Hi @Charles_Bisbee,
Thanks for reaching out! Apologies for the delay here.
According to our offline mode docs, and the behavior you're seeing in the app, offline Write queries run sequentially when the connection is restored. It sounds like you are seeing the expected behavior where the queries re-trigger when the user is back online (and then fail due to the JS query dependency).
To clarify, is your preference that the offline triggered queries do not run when the user's network status is restored to online? If so, you should be able to solve your use case by switching the offline handler to type Read
It's a bit counterintuitive since they are actually write/update queries, but this setting only impacts the offline mode. They should still write to s3 successfully when triggered while online.
Let me know if that's not quite the solution you're looking for or if this suggestion doesn't work as described in your app. Happy to take another look