Skip to main content
Applies to:
  • Plan - Any
  • Deployment - Any
  • Use case - Prevent or troubleshoot cases where Loop applies changes to the wrong project by including explicit project context and collecting the right artifacts for support

​
Summary

Loop may apply changes to the wrong project despite the intended project being selected. Retry with explicit project context and collect evidence for support.

​
What is happening

The root cause is unconfirmed. Including explicit project context in the prompt is a known workaround.

​
Fix or suggestion

​
Option 1: Include explicit project context

Approving a retry can change a scorer or automation in the wrong project again. Including a project name or ID does not guarantee the target. Do not approve unless the proposed action explicitly identifies the intended project.
  1. In the same Loop conversation, retry the request and include the project name or ID in the prompt or context field. Example: Project: "agentchat-dev" or Project ID: "proj-12345".
  2. Send the retry. When Loop requests approval, verify that the proposed action explicitly targets the intended project before approving it. If the target is not explicit or is incorrect, do not approve. Start a new thread from the intended project and contact support.

​
Option 2: Provide evidence for support

  1. Share a screenshot showing the selected project and the affected scorer or automation link if available.
  2. If the affected object’s link is unavailable because the changes were reverted, mention that when contacting support.
  3. If the issue recurs, share the Loop conversation link.

​
How to confirm it worked

  • Check the intended project’s UI to confirm the requested change appears there.
  • If the original request or retry changed another project, inspect that project and confirm the unintended scorer or automation was reverted or disabled.