fix: Datasource query doesn't fail when created At field is missing

[sondermanish]

Description

• Improvements
  Enhanced reliability for recently used datasource tracking with improved error handling and logging to ensure operations continue gracefully when issues occur.

Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.Git"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/23643457313
Commit: f32b9dd
Cypress dashboard.
Tags: @tag.Git
Spec:

---

Fri, 27 Mar 2026 11:59:31 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Improvements

  • Enhanced reliability for recently used datasource tracking with improved error handling and logging to ensure operations continue gracefully when issues occur.

• Refactor

  • Optimized datasource filtering and sorting logic for improved performance.

[coderabbitai]

Walkthrough

The markRecentlyUsed(...) method in DatasourceServiceCEImpl was refactored to directly sort and filter Datasource objects by createdAt (descending), removing null values, then set the isRecentlyCreated flag on results. Previously, the method used indexed tuples for sorting. Error handling with warning logs was added. Unused Reactor imports were removed.

Changes

Cohort / File(s)	Summary
Datasource Marking Refactor app/server/appsmith-server/src/main/java/com/appsmith/server/datasources/base/DatasourceServiceCEImpl.java	Simplified markRecentlyUsed(...) from tuple-based indexing to direct list sorting/filtering; added try/catch error handling with warning logs; removed unused Tuple2 and Tuples imports.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

Tuples once indexed, now gently retired,
Straight sorting takes place where complexity's expired.
Stream flows simpler, null guards in place,
Errors handled with grace and a logging embrace. 📋✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	⚠️ Warning	PR description lacks issue reference and technical details. The provided URL in 'Fixes' field is broken, and key implementation context from the summary is missing.	Fix the issue link to properly reference the Linear issue. Add technical context explaining the root cause and solution approach to the Description section for clarity.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly reflects the main change: fixing a failure when the createdAt field is missing by updating markRecentlyUsed() to handle null createdAt values gracefully.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/export-failure-ds-timestamp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}