Automatic Schema Refresh
Skoot refreshes each connection’s schema daily. This keeps the databases, schemas, tables, and columns available to your agent up to date.
Why Automatic Refresh Pauses
If schema refresh fails on five consecutive UTC calendar dates, Skoot pauses automatic refresh for that connection. This avoids repeatedly trying a connection that needs attention.
Failures can happen because credentials expired, permissions changed, a database is unavailable, or networking rules changed. Other schema refresh errors also count toward the five-day limit.
Repeated failures on the same UTC date count as one failed day. A successful schema refresh resets the streak, and a date with no refresh breaks it. Dates are based on when each refresh attempt started. Retries can cross a UTC date boundary.
You will see Automatic schema refresh paused in the Connected Sources list and on the connection details page.
What Still Works
The connection and its saved schema remain available. You can still run queries, edit the connection, and request a schema refresh. Queries still need working credentials, permissions, and network access.
The saved schema can become outdated while automatic refresh is paused. New or changed tables and columns will not appear until a schema refresh succeeds.
How to Resume Automatic Refresh
- Open Data Sources and select the connection.
- Check its credentials, database permissions, and network access. Update the connection if needed.
- Choose Refresh Schema from the connection actions. Saving updated connection credentials also requests a schema refresh.
- Wait for the schema refresh to succeed. Skoot removes the warning and automatically resumes daily refreshes.
Any successful schema refresh resumes automatic refresh, regardless of what triggered it. A successful connection test or query alone does not resume it. If your recovery attempt fails, automatic refresh stays paused until a refresh succeeds.