Testing and troubleshooting

Compilation checks whether supported source can be built. Page checks inspect whether deployed pages respond and may detect browser errors, missing assets, or rendering problems. Neither proves that every interaction, calculation, or access rule is correct.

1. Complete the main workflow with normal input.
2. Repeat it with missing, invalid, and boundary values.
3. Reload any screen that should show saved data.
4. Test who can read or change sensitive information.
5. Check the published version after release, not only the preview.

Open Activity and find the latest error. For FPC projects, compiler errors indicate a source problem that the agent must repair. For PHP, successful file preparation does not mean all PHP behavior was tested; a failing page may reveal an error only when that path runs.

Tell the agent which action failed and include the relevant error. Ask it to fix the problem while preserving the working behavior. If the app is marked failed because its home page does not serve, publishing is blocked until that issue is addressed.

• Question or check-in visible: answer it, or choose Resume build when available.
• Failure visible: inspect the last error and request a correction.
• Work is still active: review the newest Activity events before submitting a duplicate request.
• Credits unavailable: open Credits to review your subscription and eligible top-ups.

Builds can continue in saved segments rather than one uninterrupted request. Leaving the page is not a command to stop the build, but check the actual status when you return. Do not interpret a continuation message alone as proof that work completed.

Confirm that the latest changes were published. The live URL serves the last published version, not every preview edit. Open the live link again after publication and check the page that was changed.