[Bug]: getting 404 when running the logs command and have a zero-config function

[kfirstri]

Description

Getting function not found error when using the base44 logs command for deployed functions.

My guess is that it's related to the naming of the functions, it has slashes and we need to escape urls

Steps to Reproduce

1. create a zero config function (functions/stam/foo/entry.ts)
2. run base44 deploy
3. you can use base44 functions list to see that the function is deployed
4. run base44 logs and the function is missing

Expected Behavior

No response

Actual Behavior

No response

Environment

• OS:
• Node.js version:
• CLI version:

Error Logs

Additional Context

No response

[kfirstri]

@claude please investigate and solve this issue.

[claude]

Claude finished @kfirstri's task in 59s —— View job • claude/issue-421-20260318-1317 • Create PR ➔

---

Fix: 404 on base44 logs for zero-config functions

• Gather context and read relevant files
• Find the logs command implementation
• Find where function names are used in API calls
• Identify the missing URL encoding
• Implement the fix
• Commit and push

Root Cause

In packages/cli/src/core/resources/function/api.ts:115, the fetchFunctionLogs function was building the URL without encoding the function name:

// Before (broken)
response = await appClient.get(`functions-mgmt/${functionName}/logs`, {

// After (fixed)
response = await appClient.get(`functions-mgmt/${encodeURIComponent(functionName)}/logs`, {

Zero-config functions like functions/stam/foo/entry.ts have names like stam/foo. The unencoded slash was interpreted as a URL path separator, resulting in a request to functions-mgmt/stam/foo/logs instead of functions-mgmt/stam%2Ffoo/logs — causing the 404.

Note: deploySingleFunction and deleteSingleFunction in the same file already used encodeURIComponent correctly — this was just missed in fetchFunctionLogs.