Chains and Deployment Availability

An executable inherits its chain from its profile. Local development uses the network behind RPC_URL, which can be a testnet or local fork independently of cloud availability.

Current profile constraints

The current Roles implementation pins its contract stack to Ethereum Sepolia (11155111). New network routing or a multichain design does not make Roles profiles on that chain available automatically.

Legacy profiles have separate chain requirements. The deployment's enabled-chain list, profile creation options, verified contract stack, sponsorship configuration, and workspace plan must all permit the selected combination.

Use the console's chain picker and the management API to inspect the environment you are actually using. Do not assume that a chain listed in an SDK, RPC provider, or routing table is enabled for cloud automation.

Moving work between chains

A profile belongs to one chain. Profile reassignment is allowed only within the same chain and project. To deploy the same function on a second network, create another profile and executable, then supply the matching args, permissions, and gas settings.

For fixed addresses in permission manifests, add a mapping for each intended chain. A missing mapping blocks binding; Flow does not reuse another chain's address automatically.

Development and mainnet

Use enabled testnets while validating task logic and account permissions. Mainnet access is subject to the workspace plan and deployment configuration. The free plan's mainnet restriction is enforced during execution; changing the local RPC URL does not bypass it.

See gas modes and profiles before funding an account or enabling a schedule.