A clear path forward

What information should I send Support when a Business task is blocked?

When asking for help with a blocked Replit for Business task, include what you wanted to do, what happened instead and the chat or workspace involved.

VerifiedRH-0126v1

Those details help narrow the problem to access, setup or the task itself. A screenshot of “something went wrong” is more useful when it includes the action and time that led to it.

Include:

  • The goal and expected result.
  • The steps that led to the problem and the exact error text.
  • The time and time zone when it happened.
  • The affected chat and workspace links, plus the repo or environment if relevant.
  • What you already tried and whether it changed the result.

Share private repository details and logs only through your private support conversation, not a public post. Remove passwords, tokens, secret values and other sensitive information from screenshots and logs. Keep the original error wording so it can be matched to the right failure.

Was this page helpful?

Still stuck? Try troubleshooting with Agent.

Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.

Copying does not open Agent or send a support request. Agent availability and usage depend on your account.

Can't open your project, or need another kind of help? Get help.

Share or save this answer

Send a link

Point someone to this answer.

Save the answer

Paste the answer into your notes.

Last updated