REST API ↔ Plugin API: Do Variant Updates Propagate Consistently?
0 reputation · 23 Aug 2023, 17:05 UTC
Goal: Determine whether a batch edit performed via the Plugin API is immediately reflected in subsequent REST API calls that fetch component variant nodes.
Constraints: The REST endpoint /v1/files/:file_id/nodes returns paginated data without a total count, and plugin‑initiated property changes are asynchronous. Current observations suggest a delay of up to several seconds under heavy load, but no guarantee of eventual consistency is documented.
Uncertainty: When a plugin performs a bulk text update on 50 variants, how long does it take before a REST fetch of those variant nodes returns the updated values? Does the pagination mechanism hide latency spikes that would otherwise be observable?
Specific questions:
- What is the maximum delay between a plugin batch edit and the REST API returning updated variant data under typical production load?
- Does the REST API provide any signal (e.g., a timestamp or version field) that indicates when the data is fully synchronized with plugin changes?
- Can pagination parameters (page size, cursor) be leveraged to detect and quantify latency spikes during large fetches?
