21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
# Daily trace does not explain company-report publication failure
|
|
|
|
## Evidence
|
|
|
|
- The supplied `arr trace` for the Daily job ends `status=succeeded`, with Finance daily version 15 active, all
|
|
validation/database stages successful, and `arr.daily_version_committed` marked published.
|
|
- That trace contains no company-report job id, report month/period, per-company result, publish-stage error or artifact
|
|
publication identity. It therefore cannot explain the separate `正式表格发布失败2026-08` message.
|
|
- The trace reports `execution_scope=unknown`, `processor_mode=unknown` and `remote_dispatch=unknown` for an
|
|
`artifact_callback`, despite the current trace contract having explicit values. It also prints a full source hash in
|
|
the default CLI output.
|
|
|
|
## Logging assessment
|
|
|
|
This is a scope/observability gap, not evidence that the Daily task failed. Keep the Daily trace focused on Daily and
|
|
the outbox boundary, add monthly report id/version/as-of results to the monthly event projection, and add a separate
|
|
company-report trace with job id, source batch, period, per-company publish stage and safe error code/message. Include
|
|
runtime process/build identity and mask full hashes in default output.
|
|
|
|
No code or runtime change was made during this assessment.
|