You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/auto-graft.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,16 +163,14 @@ Auto-graft will:
163
163
3. Deploy Subgraph A and sync to block 15M
164
164
4. Finally deploy your subgraph starting from block 15M
165
165
166
-
### Automatic Pausing
166
+
### Dependency Syncing
167
167
168
-
After each dependency reaches its target block, it's automatically paused to:
169
-
-Prevent unnecessary indexing beyond the graft point
170
-
-Save computational resources
171
-
-Ensure data consistency
168
+
When a dependency reaches its target block, auto-graft will:
169
+
-Log a warning that the graft dependency has reached the required block height
170
+
-Continue indexing past the graft point to ensure the dependency remains available
171
+
-Allow the main subgraph to successfully graft from this dependency
172
172
173
-
Auto-graft will check for active allocations before pausing a dependency. If a subgraph has an active allocation (meaning it's still serving queries), it will NOT be automatically paused to prevent service disruption. This ensures that customers can continue querying subgraphs that are actively allocated.
174
-
175
-
*Note: This allocation check was introduced in v0.24.1*
173
+
*Note: Prior to v0.24.2, dependencies were automatically paused after reaching their target block. This behavior was removed to ensure better availability and prevent issues with allocations.*
176
174
177
175
## Monitoring Auto-Graft
178
176
@@ -183,9 +181,9 @@ Monitor these log messages to track auto-graft progress:
183
181
-`"Auto graft deploy subgraph dependencies"` - Process started
184
182
-`"graft dep chain found"` - Dependencies identified
0 commit comments