Configuration is not "set and forget." Instructions, knowledge sources, and Project settings need periodic review as requirements change and as the underlying source information itself changes.
Stale configuration is a quiet risk, precisely because it's quiet. A bad single-turn prompt produces a visibly bad result, and gets noticed and fixed on the spot. An out-of-date knowledge source or an instruction nobody's revisited in months can silently degrade every future conversation in that Project — with no single obviously-bad moment to trigger a fix, since each individual conversation just seems slightly off rather than clearly wrong.
Practice: periodically re-verify that uploaded knowledge and connector-sourced references are still accurate and current, and revise instructions when the underlying task or team practice has moved on since they were written.
This is, itself, the exact discipline behind how this course was built: Module 1's Appendix A is a dated reference, explicitly marked "reverify before next publish" — that's configuration maintenance, applied to this course's own content.