Processing Messages
See Errors & Warnings Catalog for the full index, and Errors & Warnings Guide for a narrative explanation of message categories, exit codes, and common fixes.
Messages from the core SSI processing engine during site deployment and include resolution.
| Message | Exit Code | Hint |
|---|---|---|
| 🕸️ Super-Simple Includes - Building site from [source] | ||
| Cache hit: [key] | ||
| ❌ Cannot canonicalize config file path [path] — nesting cycle detection may miss cycles involving this config: [I/O error message] | 6 | |
| Cannot read directory [path] while searching: [error message] | ||
| ❌ Counter source reached create_source() — counter sources are pipeline steps, not data sources | 6 | 💡 This is a programming error — counter sources must be added as PipelineStep::Counter, not via create_source() |
| ❌ Data source not found: [path] ([source type]) | 6 | 💡 Verify that the source path exists and is accessible from the source directory |
| Discovered [count] paths | ||
| ⚠️ Include source has no files: [path] | 53 | 💡 The configured include source contains no files. Any tokens referencing this source will not be replaced. |
| ⚠️ Empty source file: [path] | 53 | 💡 Under --strict, empty page or content files are rejected. Add content, remove the file, or run without --strict if an empty file is acceptable. |
| Glob expand failed for extension in [path]: [error message] | ||
| ❌ Include step reached the deploy processing loop — include steps are not valid in a deploy context | 6 | 💡 This is a programming error — include steps should never appear in the deploy step list |
| Indexed single file source: [path] | ||
| Indexed TOML file source: [path] | ||
| ❌ Inline token found but inline mode not enabled: [token] in [path] | 6 | 💡 Inline-only token positions (for example mid-sentence) need the include source to run in inline mode. Add options = ["inline"] to the include [[step]] whose emoji matches this token, not the page step. |
| Internal symlink allowed: [path] | ||
| ❌ Invalid token format: '[token]' 💡 Tokens must be an emoji immediately followed by a key identifier, with no spaces between them | 5 | 💡 In the file that contains this token, use this step's emoji immediately followed by the key, with no spaces |
| ⚠️ Invalid token positions: start=[start], end=[end], string_length=[length] | 53 | 💡 This usually indicates a corrupted or truncated source file — check the file for encoding issues |
| ❌ Leftover tokens found: [tokens] | 6 | 💡 These tokens were not replaced — check that the emoji and key name match a configured include source |
| ❌ Listed file not found in source: [path] | 6 | 💡 A path from your file or copy list is missing under the source directory. Add the file, fix or remove the list entry, or add "missing-ok" to that step's options to skip missing files. |
| TimestampSort entry has no mtime for [path] — mtime is always set during indexing for files processed by this sort strategy (programming error in sorting.rs) | ||
| Could not read [path] for title extraction — using stem as fallback title: [error message] | ||
| ❌ Nested config not found: [path] | 1 | 💡 The nested step path must contain an ssi-config.toml file |
| Nested site complete: [path] | ||
| Processing nested site: [path] | ||
| Nested site page path rejected by security guard: [path] | ||
| ❌ Nested source directory not found: [path] | 1 | 💡 Check that the nested site directory exists at the configured path |
| ❌ Nested config path ends in .toml but is a directory on disk: [path] | 1 | 💡 Use a path without the .toml extension to specify a nested directory, or rename the directory |
| ❌ Nesting cycle detected: [cycle path] | 1 | 💡 SSI supports arbitrary-depth nesting, but cycles are not allowed — check your nested step paths for circular references |
| Overwriting existing file: [path] | 💡 Multiple steps are writing to the same output path — check for overlapping destinations in ssi-config.toml | |
| ❌ Preserve processor source and destination directories are the same | 6 | 💡 The --preserve-from directory must be different from the deploy directory |
| Build finished: [summary] in [elapsed time] s. | ||
| No files processed | ||
| Processing: [step emoji] [path] ([type]) | ||
| 🔨 Processing File Source [index]/[total]: [step emoji] [path] | ||
| ❌ Deploy requires a write-capable filesystem interface but was given a read-only one | 6 | 💡 This is a programming error — deploy operations must be initialized with a Writer interface |
| Scanning for content in: [path] | ||
| Scanning source root: [path] | ||
| ❌ Failed to canonicalize path [path]: [I/O error message] | 6 | 💡 Ensure the path exists, symlinks are valid, and you have permission to traverse each component |
| Could not list keys for include source '[step emoji]' — skipping unused-key detection for this source | 💡 Unused-key checking was skipped for this include source. Check that its path is readable, permissions allow listing, and the directory or TOML source is not temporarily unavailable. | |
| Special source (no indexing): [path] | ||
| AlphabeticalSort entry has no stem for [path] — stem is always set during indexing for files processed by this sort strategy (programming error in sorting.rs) | ||
| HumanSort entry has no stem for [path] — stem is always set during indexing for files processed by this sort strategy (programming error in sorting.rs) | ||
| Navigation-source entry has no stem for [path] — stem is always set during indexing for files used in navigation (programming error in navigation/source.rs) | ||
| NumericSort entry has no stem for [path] — stem is always set during indexing for files processed by this sort strategy (programming error in sorting.rs) | ||
| TimestampSort entry has no stem_lowercase for [path] — stem_lowercase is always set during indexing for files processed by this sort strategy (programming error in sorting.rs) | ||
| System clock is set before the Unix epoch — mtime unavailable for [path] | ||
| Target path not under output root ([path] / [source]): [error message] | ||
| ❌ Template not found in content index at processing time | 6 | 💡 This is a programming error — templates must be pre-indexed before processing begins |
| Template rendering for [emoji]: no contexts to iterate | ||
| ❌ Token-scanning automaton invariant violated — duplicate keys detected in a data source | 6 | 💡 This is a programming error — data source keys must be unique |
| Token lookup failed: [token text] (source: [source]) | ||
| ❌ Include token '[emoji][token]' not found | 5 | 💡 The token appears in [path] — confirm the key matches a block file or a TOML data key for this step's emoji |
| ❌ 🐛 Include token '[token]' leaked from datasource [emoji] (should have been caught earlier) | 5 | Please report this bug |
| [[token text]] fallback: [path] | ||
| [[token text]] page-specific: [path] | ||
| [[token text]] resolved | ||
| [[token text]] UNRESOLVED | ||
| ❌ Failed to parse TOML file [path] at line [line]: [error message] | 6 | 💡 Fix the syntax near that line — unclosed strings, missing `]`/`}`, or invalid `key = value` pairs are common causes |
| TOML parse failed for [path]: [error message] | ||
| ❌ Unsupported operation '[operation]' for source '[source type]' | 1 | 💡 Check the documentation for this source type — use only operations that type implements |
| ❌ Source type '[source type]' does not support page scanning | 3 | 💡 Page scanning (processing = "page") requires a directory or TOML file source — use type = "directory" or type = "toml" |