fix(logs-page): optimize logs retrieval queries, consolidate useEffects to prevent dup calls

[icecrasher321]

Summary

• Permissions join was taking a while. Rearranged query to not have where class but filter as part of join to actually use index.
• Also removed two unused indices.
• Consolidated useEffects to make one less fetch logs call
• Remove artificial minLoadingTime timeout

Type of Change

• Other: Performance Improvement

Testing

Tested loading logs

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2025 11:22pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 1, 2025 11:22pm

[greptile-apps]

Greptile Summary

This PR implements a focused performance optimization for the workflow logs page to address slow loading times. The changes include both database and frontend optimizations:

Database Optimizations:

• Removes two unused indexes (cost_idx and duration_idx) from the workflow_execution_logs table that were adding unnecessary overhead during write operations
• Adds a new composite index workflow_started_at_idx on (workflow_id, started_at) columns to support the optimized query pattern
• Creates migration files to implement these schema changes

Query Structure Improvement:
The core optimization restructures the logs retrieval query to use join-based filtering instead of WHERE clauses. This allows the database to leverage the new composite index directly during the join operation, rather than performing expensive full table scans with post-filtering.

Frontend Optimizations:
While not visible in the changed files, the PR description indicates consolidation of useEffect hooks to reduce redundant API calls and removal of artificial loading timeouts for more responsive user experience.

This optimization follows established database performance patterns where indexes are aligned with actual query access patterns. The composite index on (workflow_id, started_at) directly supports the common use case of fetching logs for specific workflows ordered by time, which is the primary access pattern for the logs page.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it contains well-structured database optimizations
• Score reflects straightforward index management changes that follow database best practices
• No files require special attention as the migration is simple and the schema changes are conservative

_{4 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}