Investigate and refactor

Describe the pattern when a fix works temporarily, the same error returns, or each change breaks something nearby. Include previous attempts and ask Play to investigate before making another change.

Describe the pattern

This save button has failed three times. Can you investigate why and refactor the save logic?

The filter keeps breaking in different ways. Look into the data flow and redesign it to be more reliable.

This automation worked twice then stopped. Can you find the root cause and fix it properly?

I keep running into issues with this section. Can you rebuild it from scratch with a cleaner approach?

A recurring failure is a reason to investigate, not proof that a full rebuild is needed. Ask Play to:

  1. Trace the affected component, its data flow, and connected actions.
  2. Explain the likely cause and the evidence for it.
  3. Compare a targeted fix with a refactor before changing the structure.
  4. State which behavior and data must stay unchanged.

If you want to approve the approach first, say “Explain the findings and proposed changes before implementing them.”

Check the result

Retest the original failure with the same steps and data, then check related behavior. For a save fix, for example, verify that a new record appears once, contains the right fields, and can still be edited.

Report any remaining error with the new result and what changed. Use the three-part template in When something isn’t working to make the next investigation reproducible.

Still stuck? Email support@play.fast