When work gets stuck
Describe the affected step, distinguish possible causes, and find the right place for further investigation.
Describe the point where work stopped
Say what you were trying to do, which step or result is affected, and what you expected instead. Include the product version if it matters. For a website inquiry, keep that description brief and non-confidential; you do not need to provide an entire project or log.
Separate the possible causes
A source may be missing, two requirements may conflict, a tool may be unavailable, or a method may no longer fit. Another step may need a decision or permission that has not been given. These situations call for different responses; product guidance cannot diagnose an unseen project from a short description.
Check what a correction affects
The intended approach is to use the available evidence, identify the effect of the gap, and continue within the agreed permissions. A correction needs to be checked against the other requirements it could affect. Missing evidence should stay visible rather than be replaced by a plausible guess.
Take project investigation to the right place
Specific troubleshooting instructions need to match the product version. When those instructions are not available, Help can explain the limit and point to relevant guidance. Investigation of the actual project belongs in your own authorized environment; a website answer cannot certify the result or guarantee a fix.