Add dependency graph experiment and cron updates #831
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| for (const collectionId of collectionIds) { | ||
| const collectionPath = `Projects/${this.projectId}/Collections/${collectionId}/${modeCollection}`; | ||
| const query: Query = this.db | ||
| .collection(collectionPath) | ||
| .where('sys.modifiedAt', '>=', ts); |
There was a problem hiding this comment.
The dependency-graph cron only scans docs whose sys.modifiedAt is newer than the last run (dependency-graph.ts lines 205-209), but publishing a doc does not bump sys.modifiedAt—publish flows set publishedAt and copy the existing sys data (see packages/root-cms/core/client.ts publishDocs and publishScheduledDocs around lines 461‑474 and 597‑610). If a draft was last edited before the previous cron run but then gets published afterward (a common scheduled-publish path), it will never match this filter; yet the cron still advances dependencyGraphApiLastRun, so the published dependency graph silently misses that document until someone edits it again.
Useful? React with 👍 / 👎.
Summary
Testing
Codex Task