chaim
b05e1c8488
The floating chat called Espo.Ajax.postRequest with timeout:180000, which is shorter than the agentic loop's worst-case latency. On 2026-05-13 a prod request to generate a direct-access report sat 227s in the first ai-gateway iteration (large skill+context payload), so the browser fired the .catch() handler at 180s and rendered "שגיאה בתקשורת" — even though the backend completed the work 47s later (report attached to case 42). Changes: - floating-chat.js: timeout 180000 → 600000 (matches the PHP curl timeout already set to 600s in SmartAssistantService.php:521). - After 60s the spinner label swaps to a "still working" hint so the user knows long requests are normal, not stuck. - i18n: new SlowHint label in en_US + fa_IR (the project uses fa_IR as the Hebrew slot). Refs Task Master #3 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 lines
369 B
JSON
15 lines
369 B
JSON
{
|
|
"name": "SmartAssistant",
|
|
"module": "SmartAssistant",
|
|
"description": "Unified AI Assistant for Legal CRM — floating chat with case memory, office alerts, and AI Gateway integration",
|
|
"author": "klear",
|
|
"version": "2.8.2",
|
|
"acceptableVersions": [
|
|
">=8.0.0"
|
|
],
|
|
"releaseDate": "2026-05-13",
|
|
"php": [
|
|
">=8.1"
|
|
]
|
|
}
|