When something isn't working

Tell Play what you did, what you expected, and what happened instead. Include the affected app or task and the exact error message rather than only saying “it is broken.”

Explain the situation

Include three things:

  1. What you did, including the relevant action or request.
  2. What you expected to happen.
  3. What happened instead, including the exact error if there was one.

For a button that does not save:

What I did: I clicked Save on the new contact form.
What I expected: The contact should appear in my contacts list.
What happened: The form stayed open and the contact did not save.

For a filter:

What I did: I selected High Priority in the filter dropdown.
What I expected: The table should show only high-priority items.
What happened: The table still shows all items regardless of priority.

For an automation you configured:

What I did: I added a row to the spreadsheet used by the email automation.
What I expected: A confirmation email should go to the address in that row.
What happened: No email was sent.

Mention the connected account, relevant record, and when the problem occurred. For an automation, explain how it was configured to run; do not assume that adding a row triggers a task unless that trigger is set up.

Follow up

Include the steps you have already tried and visible clues such as “The error says Connection failed.” Ask Play to explain the proposed fix, then repeat the original steps after it makes the change.

If the problem returns, try:

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

The filter still isn’t working. Look into the data flow and fix the root cause.

This keeps breaking. Can you redesign this part to be more reliable?

See Investigate and refactor for recurring problems, or Common issues for account, connection, and access checks.

Still stuck? Email support@play.fast