Block reference / App Management

Save resource

Back up the account on the phone into a new snapshot and give it back to its pool.

Only inWarpX Phone

Save resource ends an account's turn. It backs the pool's apps up off the phone into a new snapshot — what Load resource puts back next time — gives the account back to its pool, counts the use and starts its rest. It also says how the account came off: ready for another turn, or held back for a checkpoint or a ban.

The account's apps are copied off into a new snapshot before the next account is loaded.
The Save resource block's settings, filled in as in the example below.

Settings

Give it back as

Ready loads it again once it has rested. Checkpoint, Banned and Disabled keep it out of loads until it is set back to ready on the Resources page.

ExampleReady — loaded again after its rest
Note (optional)

Shown beside the account on the Resources page — why it was checkpointed, say. Takes variables.

ExampleAsked for a selfie
Back its apps up first

Off, the account goes back with its last snapshot, and what was done since Load resource is not kept.

ExampleChecked
Delay (ms)

A pause after the block finishes, before the next block starts. Write one number such as 1000, or a range such as 1000,3000 to pick a random pause in that range on each run.

Example0

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Hands on the account's label as {{prevBlockData}}. Leaves by its single output.

Example: Mark an account that hit a checkpoint

  1. Load resource
  2. Conditions
  3. Save resource
Where Save resource sits in the example workflow.
  1. After Load resource, look for the checkpoint screen with an element block.
  2. When it is there, add Save resource with Give it back as Checkpoint and a note.
  3. Otherwise, do the account's work and add Save resource with Ready.

Good to know

  • The snapshot keeps the app's private data, where it is signed in: root only. Without root the save fails rather than keep a snapshot that would load signed out.
  • A backup that fails gives the account back with its last snapshot and status, and the block fails with BACKUP_FAILED.
  • The pool keeps its newest snapshots — three unless set otherwise — and drops the older ones.
  • With nothing loaded on the phone (or its hold ran out) the block fails, saying so.
  • A workflow that was not edited on this computer (from the Appstore, a file or the assistant) asks you to allow this block before its first run, in a window that lists what it will do. Blocks you set up in the editor are approved as you edit them, so your own workflows never ask; changing the block's settings asks again.
  • There is no Device field: the block acts on the run's phone — the one picked in the editor's toolbar, or each phone ticked for Run automation in the Control Center or named in an API run.

See also

  • Load resource — Take the next free account from a resource pool and put it on the phone: its device, its proxy and its signed-in apps.
  • Backup — Copy one app, or every app you installed, from the phone to a folder on this computer.