...
The issue reproducible only within the first 15 minutes after creation/modification.
Root Cause
The full-text search mechanism in the FirstBit platform operates asynchronously. When a new object is created, the data is saved to the main database instantly, but it is not immediately added to the full-text search index. The index update is handled by a separate background process (a scheduled job).
Diagnostics
Verify the item exists in the database.
Confirm the new Item is present by navigating directly to it (e.g., via the Items list or a direct link). If it opens and displays correctly, the issue is not about data creation but about search indexing.Check the full-text search index status.
- Go to Administration → General Settings → Full-text search of data → Configure.
- Look at the index status field. If it shows “Needs update” or “Out of date,” the index hasn’t yet included recent changes.
- Note the timestamp of the last successful index update. If it’s older than the time the Item was created, that confirms the delay.
Review the background job schedule and history.
- Navigate to Administration → Maintenance → Scheduled and Background Jobs.
- Find the job named Update Full-Text Search Index (name may vary slightly by configuration).
- Check its schedule (how often it runs) and recent execution history (last run time, status, errors). A long interval or a failed/stalled run explains why the new Item isn’t in the index yet.
Resolution
Related Materials
Product / Configuration
Functional Area / FirstBit Software Section
...