Offline mode, API throttling, and import workarounds
confusiongeneralUsers report recent failures in offline mode, REST API throttling, and batch imports, with available but suboptimal legacy path workarounds.
Evidence (24 linked events)
Every mention below links to its original post — insights in Loop are never unsourced.
“Can confirm — offline mode started failing for us around the same date.”
“Workaround: avoid airplane-mode support and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid airplane-mode support and use the legacy path. Not great, but unblocks you.”
“Can confirm — exported report columns started failing for us around the same date.”
“Can confirm — the 429 throttling on the REST API started failing for us around the same date.”
“Workaround: avoid a batch API for imports and use the legacy path. Not great, but unblocks you.”
“Can confirm — two-way Slack sync started failing for us around the same date.”
“Can confirm — background sync on mobile started failing for us around the same date.”
“Workaround: avoid the 429 throttling on the REST API and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid duplicate detection on import and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid the dashboard on slow connections and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid the authenticator app pairing and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid chart rendering speed and use the legacy path. Not great, but unblocks you.”
“Workaround: avoid caching data locally and use the legacy path. Not great, but unblocks you.”
“Can confirm — caching data locally started failing for us around the same date.”
“Workaround: avoid mapping custom fields and use the legacy path. Not great, but unblocks you.”
“Can confirm — exact phrase search started failing for us around the same date.”
“Can confirm — account lockout after password reset started failing for us around the same date.”
“Can confirm — searching within archived items started failing for us around the same date.”
“Kudos on the team offsite. Whoever built the video call, great work!”
“Huge thanks for the newsletter — it's fantastic. the team offsite is so smooth.”
“I can't figure out the team offsite? I've read the docs twice. A pointer to the coffee docs would help.”
“Kudos on the video call, it saved me hours this week. the team offsite is so smooth.”
“Absolutely love the monitor arm — it's fantastic. the team offsite rocks.”