You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐛 Bug - Bookmark toggle returns 404 and does not save bookmarks #2682
Users are unable to bookmark rules in Rules V3 (TinaCMS). Clicking the bookmark button does not perform any action. Browser console logs show an error when toggling bookmarks, returning an HTTP 404 response. The bookmark functionality should successfully save and toggle bookmarks without console errors.
Acceptance Criteria
Clicking the bookmark button successfully saves or removes a bookmark for a rule.
The bookmark state updates correctly in the UI after toggling.
No HTTP 404 error is returned when toggling bookmarks.
No console errors are displayed when using the bookmark feature.
Bookmarked items persist after page refresh if persistence is expected by the application design.
Reproduce Steps
Open the Rules V3 (TinaCMS) website.
Navigate to any rule page.
Open browser developer tools.
Go to the Console tab.
Click the bookmark button on the page.
Observe that no bookmark action occurs.
Observe the console error indicating 'Error toggling bookmark' with an HTTP 404 response.
Screenshot
Figure: Bookmark button triggers 404 error
Reacted by Larry Carland [SSW], Adam Cogan [SSW], Tiago Araújo [SSW], Chloe Lin and Brady Stroud [SSW]
✅ Done — Fixed by moving NEXT_PUBLIC_API_BASE_URL to the repository level.
Root cause: NEXT_PUBLIC_API_BASE_URL was configured as an environment-level variable, but the build job did not declare an environment, so GitHub Actions did not expose it. As a result, the value was empty, and the “Add bookmark” request fell back to /api/... on the website’s own domain, returning a 404 instead of calling the Functions app.
Activity
Aibono1225 commentedon Jul 24, 2026
✅ Done — Fixed by moving
NEXT_PUBLIC_API_BASE_URLto the repository level.Root cause:
NEXT_PUBLIC_API_BASE_URLwas configured as an environment-level variable, but the build job did not declare anenvironment, so GitHub Actions did not expose it. As a result, the value was empty, and the “Add bookmark” request fell back to/api/...on the website’s own domain, returning a 404 instead of calling the Functions app.