log caught redis_version_cached exception

[adamsachs]

Description Of Changes

We're swallowing caught Exceptions with only a DEBUG log that doesn't include the underlying exception information.

Code Changes

• log at EXCEPTION level to include full stack trace of underlying exception
• for production environments, I think the stack trace is suppressed - so long top-level exception summary within log message.

Steps to Confirm

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Mar 2, 2026 4:44pm
fides-privacy-center	Ignored		Mar 2, 2026 4:44pm

[erosselli]

ship it!

[greptile-apps]

Greptile Summary

This PR improves exception logging in the Redis version cache utility by upgrading from DEBUG to EXCEPTION level logging. The changes ensure that when Redis becomes unavailable, the full exception details and stack traces are properly captured in logs, making debugging production issues significantly easier.

Key changes:

• Changed logger.debug() to logger.exception() for Redis connection failures
• Added exception object capture (except Exception as e) to include exception details in log messages
• Maintains backward compatibility - the fallback behavior (returning stale cache or calling function directly) remains unchanged

Impact:

• Better observability in production environments where Redis connectivity issues occur
• No functional changes to the caching mechanism or fallback logic
• Follows existing logging patterns used elsewhere in the codebase (e.g., memory_watchdog.py, rate_limit.py)

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• This is a straightforward logging improvement with no functional changes to the caching logic. The modified code is well-tested with comprehensive test coverage, and the logging pattern follows existing conventions in the codebase. The change only affects observability and debugging capabilities without altering any business logic or error handling behavior.
• No files require special attention

Important Files Changed

Filename	Overview
src/fides/api/util/redis_version_cache.py	Changed exception logging from DEBUG to EXCEPTION level to capture full stack traces and exception details when Redis is unavailable

_{Last reviewed commit: a5854db}

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

inconsistent string formatting - remove f prefix to match codebase pattern

Suggested change

	logger.exception(
	"redis_version_cache '{}': Redis unavailable, returning stale cached value. Exception: {}",
	cache_key,
	e,
	)
	logger.exception(
	"redis_version_cache '{}': Redis unavailable, returning stale cached value. Exception: {}",
	cache_key,
	e,
	)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[greptile-apps]

inconsistent string formatting - remove f prefix to match codebase pattern

Suggested change

	logger.exception(
	"redis_version_cache '{}': Redis unavailable and no cached value, calling function directly. Exception: {}",
	cache_key,
	e,
	)
	logger.exception(
	"redis_version_cache '{}': Redis unavailable and no cached value, calling function directly. Exception: {}",
	cache_key,
	e,
	)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[adamsachs]

@greptile

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[adamsachs]

bypassing merge queue and branch protection rules (at least, attempting to!) in order to get this into main ASAP. this will give us more insight into the problem on our nightly environment, which may also be impacting a production customer environment