[Bug]: HTTP 404 When Editing Inactive Resource from Admin UI

[rakdutta]

When attempting to edit an inactive resource from the Admin UI, the application returns an HTTP 404 Not Found error. This prevents users from opening the edit screen for any resource that is currently marked as inactive.

Steps to Reproduce

1. Go to Admin UI → Resources
2. Navigate to the Inactive Resources tab
3. Click the Edit button for any inactive resource
4. UI attempts to load the resource details
5. System returns HTTP 404

Expected Behavior

The inactive resource should be retrievable, and the edit page should open normally.

Actual Behavior

A 404 error is returned, and the Edit screen does not load.

Impact

• Inactive resources cannot be edited or reactivated
• Admin workflow is blocked
• Requires backend or routing fix for inactive resource handling

Possible Causes

• Backend endpoint does not fetch resources with enabled=false
• Incorrect route or resource URI mapping for inactive state
• Missing database filter including inactive records

Supporting Screenshot

If you want, I can also prepare a PR description, root cause analysis, or test case list for this issue.