Skip to main content
An instance runs one exact automation graph version. It controls status, launch limits, cooldown, and AI credit limits. Variable defaults belong to the graph version, not to an individual instance.

​
Open Instances

Open Scrapist, then choose Manage to search graphs and instances. Expand a graph for quick controls, or open the graph editor and select Instances for its full instance history.

​
Understand Instance Status

Some administrative environments also show Test Active. Use it only when your account has been instructed to test that status.

​
Create An Instance

1

Select a graph version

Open the exact version you tested and compiled.
2

Open Instances

Select Instances, then click New Instance.
3

Set operational limits

Configure an instance cap, credit limit, and cooldown when the automation should stop or slow down after activity.
4

Review the graph defaults

Under Build, confirm the selected version’s author lists, wallets, amounts, launchpads, fees, and enable switches. Every instance targeting that version uses the same variable defaults.
5

Create and activate

Create the instance, then choose Activate when you are ready for matching live events.
An active instance can run launch and trading actions without another prompt. Confirm wallet balances, amounts, fees, platforms, and limits before activation.

​
Monitor Usage And Limits

Instance controls show:
  • The graph version and current status.
  • Instance cap and completed deploy count.
  • Credit limit and credits spent.
  • Cooldown.
  • Recent runs and status changes.
Open Monitor when you need to search across runs, launches, trades, responses, and failures.

​
Change Or Retire An Instance

  • Deactivate or Pause before editing the graph version or its shared defaults.
  • Change shared variable defaults only after confirming that no active instance is relying on that graph version.
  • Archive an inactive instance when you want to keep its history out of the active list.
  • An instance with run history may be archived instead of permanently deleted.
Create a new graph version for behavior changes. Test and compile it, then move live operation deliberately instead of modifying the version currently in use.