You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d6203c3
Browse filesBrowse the repository at this point in the historyBrowse files
A large part of Sim runs on a schedule rather than in response to a user request: scheduled workflows, every polling trigger, connector syncs, the outbox, data drains, and retention. All of it is driven by **HTTP endpoints that something external must call on a timer**.
8
+
A large part of Sim runs on a schedule rather than in response to a user request: scheduled workflows, every polling trigger, connector syncs, the outbox, data drains, and retention. The default self-hosted scheduler calls **HTTP endpoints on a timer**. Deployments using Trigger.dev also run the document-indexing tasks described below.
9
9
10
10
Both deployments ship a scheduler and enable it by default: Kubernetes as CronJobs, Docker Compose as a `cron` service. Both authenticate with `CRON_SECRET`, and both use the same schedules.
11
11
@@ -146,3 +146,16 @@ Scheduled execution volume is bounded per app instance by:
146
146
</Callout>
147
147
148
148
Raise the schedule limit only alongside memory headroom: concurrent executions run in the app process, so throughput is bounded by the pod's memory before it is bounded by this number.
149
+
150
+
## Trigger.dev document indexing
151
+
152
+
If Trigger.dev is enabled, document indexing uses a durable dispatch queue. Large imports wait in the database, and organizations share the existing worker budget. Temporary provider-capacity waits retry later without keeping a worker occupied. Default self-hosted installs continue to process documents in the app.
153
+
154
+
When upgrading a deployment that uses Trigger.dev:
155
+
156
+
1. Apply the database migrations before starting the new workers or application.
157
+
2. Deploy the Trigger tasks from the same revision before deploying the application. New workers accept existing queued jobs as well as the new compact document references.
158
+
3. Confirm the application and workers use the same database and Trigger environment. Verify that the `knowledge-document-dispatch-schedule` task is enabled; it runs every minute to resume delayed work and recover missed dispatch notifications.
159
+
4. Sync a small source and confirm its documents become searchable. A successful sync only confirms the source was fetched; indexing can still be running.
160
+
161
+
Enqueue and completion notifications normally start the next work promptly. The minute schedule provides recovery when a notification is missed; it does not repeatedly download documents. Keep the updated workers running until their durable queue has drained before rolling them back.
3. Ask a teammate with different source access to repeat the search. Documents restricted to you should not appear for them.
96
96
4. Change or remove a test document's access in the source and check again after the next completed content and permission refresh.
97
97
98
-
Search runs background syncs on an hourly schedule. Large sources, provider limits, and indexing queues can delay completion. Results are indexed copies, so edits and access changes are not fetched live for every query. Admins can inspect errors and progress under **Manage**.
98
+
Search runs background syncs on an hourly schedule. Large sources, provider limits, and indexing queues can delay completion. Results are indexed copies, so edits and access changes are not fetched live for every query.
99
+
100
+
## If indexing needs attention
101
+
102
+
A completed sync means the source was checked; some documents may still be indexing. The source row shows how many documents you can search and whether indexing failed for any documents you can access.
103
+
104
+
As an admin, open **Manage → Settings → Documents → Failed** to inspect those files. Select **Retry indexing** beside a file to try again. **Exclude** removes a file from search; use the **Excluded** tab and **Restore** to include it again. Fix a disconnected account or source configuration before retrying a sync that needs attention.
105
+
106
+
Temporary indexing-capacity waits retry automatically in the background. If automatic retries are exhausted, the document appears as failed so an admin can retry it. Other searchable documents remain available while this work finishes.
99
107
100
108
These guides cover permission-aware Search sources. For a general knowledge base used by workflows, see [Knowledge-base connectors](/knowledgebase/connectors); its workspace access settings are a separate choice.
0 commit comments