Troubleshooting

What the Lab's error and status messages mean and what to do about each one.

Sign-in messages are covered in Signing in and access. Everything else you're likely to see in the Lab is below.

Message	What to do
“You're out of usage — top up to keep building.”	Your build usage is used up. Input tweaks, exports and backtests still work. See Usage and limits.
“You already have builds running — let them finish first.”	A build is still running, maybe in the background or another tab. Let it finish or press Stop.
“Too many builds just now — give it a moment and try again.”	Wait a minute, then send again.
“This indicator changed in another tab. Reopen it to use the latest revision.”	Reopen it from Saved or Your indicators and carry on from the latest version.
“This build stopped safely. Your last complete revision and chart are unchanged.”	The build ended without a new version, and nothing you had is lost. Use Try again on the build card if it's there, or reword the request.
“That build record expired or could not be found.”	Press Try again to send the request again.
“Could not save this revision — it will retry on your next change.”	It saves again on your next change. If it keeps showing, reload the Lab.
“Daily code limit reached — you can fork …”	You've used today's forks. It resets at midnight UTC. In the Backtester the same limit reads “You've hit today's code-unlock limit …”.
“Forking another member's indicator is part of membership — your own builds and exports stay free.”	Your account doesn't include forking. See Membership and billing.
“This build is very close to a protected indicator in our catalog. …”	Change the logic in the Assistant: different signals, levels or drawings. See Own code and protected builds.
“Saved privately — protected indicators can be used in both Labs, but cannot be published.”	Protected builds can't be published. You can still use and backtest them.
“Imported Pine and its derived artifact stay private and cannot be published.”	Imported scripts and their versions stay private. You can still export and backtest them.
“The community request could not be completed.” when publishing	Often the build is a near-copy of another member's indicator or of a protected one. Fork the original to build on it, or change the logic. Otherwise, try again.
Import messages such as “Choose a .pine file.”	See Starting from your own Pine.
“Session expired — please log in again.” or “Session expired — sign in again to reconnect to your saved build.”	Sign in with Discord again. A build that was running keeps going on our side, and the Lab reconnects to it.
Indicator could not render	Press Try again. If it keeps failing, describe what you see in the Assistant so the script gets fixed.
Connection interrupted	Your last chart is kept. Check your connection and press Try again.