Failover Instance
memorystore.failover_instance
ActionGoogle Cloudconnection required
Calls Memorystore REST POST /instances/{instance}:failover.
Initiate a manual failover of a Standard-tier Redis instance.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Memorystore for Redis
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Region, e.g. us-central1 (overrides connection). | string | No | — | — | — |
instance Redis instance id. | string | Yes | — | — | — |
data_protection_mode Failover data protection mode. | string | No | LIMITED_DATA_LOSS | one of "LIMITED_DATA_LOSS", "FORCE_DATA_LOSS" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data_protection_mode": "LIMITED_DATA_LOSS"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
operation | string | — |
done | boolean | — |
{
"done": false,
"operation": ""
}Related Google Memorystore for Redis nodes
See Failover Instance run in a workflow.
In a technical demo we add the Google Memorystore for Redis connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.