Common Issues

Missing functionality

Overview

When a feature you described doesn't appear in your app - or doesn't work as expected - it's usually due to one of a few common causes. This page walks you through diagnosing the issue and requesting a rebuild or clarification.

Note

Most missing functionality is resolved by rephrasing your request or explicitly calling out the feature in a follow-up chat message.


Common reasons features go missing

The agent misunderstood the scope Natural language can be ambiguous. If you said "add user profiles," the agent might have built a basic profile page but skipped avatar uploads, bio fields, or edit functionality.

The feature was deprioritized Emergent's agents prioritize core flows first. Secondary features - like admin dashboards, analytics, or "nice-to-have" UI polish - may be deferred or omitted if the initial build focused on MVP functionality.

A dependency wasn't clear Some features require scaffolding. For example, "send email notifications" needs an email service integrated, and "save preferences" needs a database schema. If you didn't mention the underlying requirement, the agent may have skipped the feature.

The feature exists but isn't visible Check that you're testing the right screen, user role, or device form factor. A feature built for mobile may not render on desktop, or an admin-only button may be hidden for regular users.


Step-by-step diagnosis

1

Verify the feature was in scope

Re-read your original chat prompt and any follow-up messages. Did you explicitly request the feature, or was it implied? Agents work best with direct, specific instructions.

2

Check the current build

Open the live preview or published app and navigate to where the feature should appear. Test all relevant user roles, screen sizes, and edge cases (e.g., empty states, logged-out views).

3

Review the build log (if available)

Some workspaces surface build summaries or agent notes in the chat history. Look for messages like "skipped X due to Y" or "deferred Z for next iteration."

4

Search the codebase

Use the workspace file tree or search to look for related code. Note that the code editor (including the file tree) is available on all plans including Free; only GitHub push requires Standard+. If the feature is partially implemented - like a backend route without a UI - you'll find clues in api/, components/, or pages/ directories.


Requesting a fix or rebuild

Once you've confirmed the feature is missing or incomplete, ask the agent to build it in a new chat message. Use clear, actionable language:

PLAINTEXT
Add a "Save Draft" button to the blog post editor.
It should save the current title and body to the
database without publishing. Show a success toast
when saved.

Be explicit about acceptance criteria:

  • Where should the feature appear? (e.g., "in the top-right of the editor header")
  • What should it do? (e.g., "POST to /api/drafts, store in MongoDB")
  • What should the user see? (e.g., "a green checkmark icon and 'Draft saved' message")

Tip

If the feature depends on a database collection, API endpoint, or third-party service, mention it up front. For example: "Use the drafts collection in MongoDB" or "Integrate Stripe for payment processing."


When functionality is partially built

Sometimes a feature exists in the backend but lacks a UI, or vice versa. Here's how to complete it:

SituationNext step
Backend route exists, no UI"Create a form in components/DraftEditor.tsx that calls POST /api/drafts and shows a success message."
UI exists, no backend"Implement the /api/drafts endpoint: accept title and body, save to MongoDB drafts collection, return 201."
Feature works on web, missing on mobile"Add the Save Draft button to the mobile layout in DraftEditor.tsx. It should match the web behavior."

Common gotchas

If you asked the agent to "simplify" or "redesign" the app, it may have removed features you wanted to keep. Check the chat history for messages like "removed X to simplify Y."

Fix: Explicitly ask to restore it: "Bring back the Save Draft button and keep the new design for the rest of the editor."

Some functionality - like admin panels or payment flows - may be gated by environment variables or user roles. Check your .env file (accessible via the VS Code editor, available on all plans) and any role-checking logic in the code.

Fix: Update the relevant env var or user role in your database. See Database (MongoDB) for how to modify user records.

Features like email, payments, or SMS require API keys and service setup. If the agent built the integration but you haven't added credentials, the feature will fail silently.

Fix: Add the missing API key to your .env file or workspace secrets. See The Universal LLM Key for an example of secret configuration.


Escalation

If you've followed the steps above and the feature still doesn't work:

  1. Describe the exact behavior you're seeing (e.g., "clicking Save Draft shows a 500 error in the console").
  2. Share the expected behavior (e.g., "it should save to MongoDB and show a success toast").
  3. Ask the agent to debug: "Check the /api/drafts endpoint and the DraftEditor component. The save button isn't working."

Warning

If the agent repeatedly misunderstands or skips the same feature, try breaking the request into smaller, sequential steps. For example: "First, create the database schema for drafts. Then, build the API endpoint. Finally, add the UI button."


Was this page helpful?

Related pages