Jarvis Refresh

Step 2: Assess Current Freshness

Calculate days since last pull for each instance. Present freshness status.

Step 3: Present Bundle Menu

Show available refresh bundles from status.json with current state:

DATA REFRESH MENU
─────────────────────────────────
Bundle              Tables  Last Refreshed
─────────────────────────────────
[1] ITSM Core       8       [date or NEVER]
[2] Administration  4       [date or NEVER]
[3] Catalog         5       [date or NEVER]
[4] Security        2       [date or NEVER]
[5] Knowledge       1       [date or NEVER]
[6] Integration     2       [date or NEVER]
[7] Assignment      1       [date or NEVER]
[8] CMDB            1       [date or NEVER]
[9] Changes         1       [date or NEVER]
[F] Full Refresh    ALL     [date or NEVER]
─────────────────────────────────
Recommendation: [suggest which bundle based on staleness]

Which bundle? (enter number or F)

Step 4: Execute Refresh

After Chadron selects a bundle:

1. Check if ServiceNow connector script exists at scripts/servicenow/
2. If MCP server is configured, use live API queries
3. If no MCP, guide Chadron through manual export steps or run the connector script
4. After data lands, update Jarvis/status.json with new pull timestamp

Step 5: Confirm

Report what was refreshed, record count, and any errors encountered.

Important

• Always check credentials exist before attempting connection
• If proxy-restricted (Cowork VM), note that outbound HTTP may fail
• Never store credentials in logs or output