Troubleshooting

This page captures common failure modes that this repo is intended to prevent.

Transform Works Locally But Fails In API

Typical causes:

• hidden package dependencies
• un-namespaced function calls
• local helper scripts not committed
• local data reads embedded in transform logic

Model And Transform Are Out Of Sync

Typical symptom:

• transformed data does not contain the variables expected by the model object

Typical cause:

• the analyst changed the transform logic or variable representation without rebuilding or updating the model artefact consistently

Decomp Fails In Packaged Runtime

Typical causes:

• formula parsing edge cases such as lead() or I(...)
• mismatched mapping table
• model and decomp wrapper not using the same representation
• hidden reliance on attached packages or local session state

Week Start / Calendar Problems

Typical symptom:

• fixed-forecast or future data is shifted, duplicated, or partially NA

Typical cause:

• one part of the workflow assumes Monday weeks while the market uses Sunday weeks, or vice versa

Local Script Drift

Typical symptom:

• product team fixes do not match the analyst’s “real” script

Typical cause:

• local SharePoint or Windows-drive copies acting as private forks

First Questions To Ask

1. What is the authoritative Git version?
2. What exact model object is being used for predict?
3. Is the same model object used for decomp?
4. Does transform() produce the variables the model actually expects?
5. Are there any hard-coded local dependencies left?