Titanium SDK 10.0 Cloud Offline Sync: Unresolved Cost‑Control Decision

Goal

Determine how the Cloud module’s offline mode in Titanium SDK 10.0 influences server costs for low‑traffic workloads and identify the missing decision point that prevents cost‑predictability.

Constraints & Uncertainty

• The SDK documentation specifies that changes made offline are queued for later sync but does not define the exact trigger for automatic synchronization when connectivity is restored.
• It is unclear whether automatic sync is limited to the free Cloud tier or applies to paid plans, leaving the cost per request ambiguous.
• Platform differences between iOS and Android may affect when the sync occurs (e.g., app resume, background fetch, or explicit sync call), further complicating cost estimation.

Key Decision Point

Without a clear definition of the automatic sync trigger and its relation to tiered pricing, developers cannot reliably predict or control the number of outbound requests and the associated data transfer costs for low‑traffic applications.

Questions

1. What specific event or lifecycle hook initiates automatic synchronization after network connectivity is restored?
2. Does automatic sync count toward the request limits of the free Cloud tier, or is it reserved for paid plans?
3. Is there a documented configuration option to disable automatic sync entirely in order to manage costs manually?