microsoft / microsoft/PowerPlatformConnectors

[BUG] Brave Search connector: UI Language dropdown does not follow Brave API Market Codes (e.g., missing ja-JP)

Open
#4,038 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Independent Publisher Connector

Name of Connector

Brave Search (Independent Publisher)

Describe the bug

Summary
The "UI Language" parameter in the Search web action shows a dropdown that does not match Brave Web Search API's Market Codes. For example, "ja-JP" is not available and users must pick "Custom value" and type "ja-JP" manually.

Steps to Reproduce

  1. In Power Automate or Logic Apps, add the Brave Search – Search web action.
  2. Open the UI Language dropdown.
  3. Try to select "ja-JP".

Actual Behavior

  • The dropdown lists values that look like language codes (e.g., en, ja, zh-hans) and "ja-JP" is missing.
  • Users have to select "Custom value" and type "ja-JP" to get the expected behavior.

Expected Behavior

  • The UI Language dropdown should list Brave API Market Codes (locale), e.g., en-US, ja-JP, it-IT, ko-KR, etc., OR the doc should clearly instruct users to enter a valid Market Code.

Impact

  • Misleads users into thinking ui_lang accepts language codes.
  • Causes inconsistent requests and localization.

Proposed Fix

  • Replace the dropdown items with Brave's Market Codes, or remove incorrect presets and document that ui_lang requires a Market Code.
  • Clearly distinguish parameter types in docs:
    • ui_lang → market/locale code (e.g., en-US, ja-JP)
    • search_lang → language code (e.g., en, ja)
    • country → country code (e.g., US, JP)

References

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce
  1. Create a Power Automate flow (or Logic Apps standard/consumption workflow).
  2. Add the Brave Search – Search web action.
  3. Open the UI Language dropdown.
  4. Try to select ja-JP (or other locale/market codes such as en-US, it-IT).
  5. Observe that ja-JP is not in the list and you must choose Custom value and type ja-JP manually.
  6. Run the action with ui_lang=jp vs ui_lang=ja-JP and compare results.
Expected behavior
  • The UI Language dropdown should list Brave API Market Codes (locale) such as en-US, ja-JP, it-IT, ko-KR, etc., or the doc should clearly instruct users to enter a valid Market Code.

  • Values offered in the dropdown must match (or be auto-validated against) Brave’s Market Codes list.

  • Parameters should be clearly distinguished:

    • ui_langmarket/locale code (e.g., ja-JP)
    • search_langlanguage code (e.g., ja)
    • countrycountry code (e.g., JP)
Environment summary
  • Surface: Power Automate (cloud) / Azure Portal – Logic Apps
  • Connector: Brave Search (Independent Publisher)Search web action
  • Region/tenant: e.g., Asia / Commercial tenant (replace if different)
  • Browser: e.g., Chrome 129 (replace with yours)
  • No CLI used; repro is fully in the UI.
  • Workaround: selecting Custom value and entering ja-JP works.
Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Brave Search connector's Search web action and compare the UI Language dropdown values with the linked Brave Market Codes documentation. Done means the dropdown uses locale codes such as ja-JP, or the connector documentation clearly explains how ui_lang, search_lang, and country differ and how to enter a custom value.

Written by the indexing model from the issue text.

Assessment

Domain
api, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.