How to Fix INVALID_NAVIGATE_ACTION_NEXT_SCREEN_NAME: Unknown Screen ID in Navigation

If you're working with a flow JSON file or building an app using a low-code/no-code platform, and you encounter this error:

INVALID_NAVIGATE_ACTION_NEXT_SCREEN_NAME

Unknown screen ids found: [screenNames].

It means that the screen you're trying to navigate to doesn't exist in your current flow configuration. Fix it by either creating the missing screen or correcting the screen name in your navigation action.

In this blog, we’ll walk through what causes this error, how to fix it, and how to avoid it in the future.

What This Error Means

This error occurs when a navigation action references a screen name that isn't defined anywhere in the flow JSON.

To put it simply:
You’re telling the app to navigate to a screen that hasn't been created or included in your flow.

Common Causes

Typos in the screen name
Renaming a screen but forgetting to update its references
Copy-pasting code and forgetting to replace placeholder screen names
Deleting a screen without cleaning up navigation actions

Example of the Problem

Here's an example where this issue happens:

"on-click-action": {
  "name": "navigate",
  "next": {
    "type": "screen",
    "name": "not_present"
  },
  "payload": {}
}

But in your screens array, there is no screen with the ID not_present. So when the app tries to navigate, it fails because it can't find the destination screen.

How to Fix It

There are two main ways to fix this:

1. Add the Missing Screen

If you meant to navigate to a screen that hasn’t been added yet, simply define it in your flow JSON:

{
  "id": "not_present",
  "layout": { ... },
  "data": { ... }
}

Make sure the id matches exactly—screen IDs are case-sensitive.

If you mistyped the screen name, correct it to point to an existing screen:

"next": {
  "type": "screen",
  "name": "SECOND_SCREEN"
}

Double-check spelling, capitalization, and that the screen ID you're using actually exists in your screens array.

For more troubleshooting tips related to WhatsApp Business API, check out heltar.com/blogs.