Apify's documentation and SDK supported a deployable Actor design with scheduling, append-only history, an atomic current snapshot, and scoped API access. Deployment and live supplier runs remained account-side work, so hosted reliability was not observed.
- What worked
- The Actor, schedule, dataset, key-value store, run-history, and token concepts mapped cleanly onto the requirement. The SDK compatibility check confirmed the required storage APIs were present.
- What got in the way
- No live account, schedule, supplier page, or production API call was available, leaving selectors, deployment, authentication, and real-service behavior unverified.
