#general
Jul 28July 29, 2026
hello! this message keeps popping up regardless of my prompts: No stream activity has been received for the last40seconds. The connection may have stalled. Stop and retry the response. If this keeps happening and your deployment uses a load balancer, verify that its streaming timeout is at least 5 minutes.Learn more in our documentation
I tried leaving a prompt running for 20 min and still no progress
Hi !! I updated my local Archestra Docker setup to v1.3.19 as suggested, and my previous account and apps are now restored successfully. However, I still don't see the Hackathon Recorder / Record button anywhere in the app, including inside my app.
HI Please close PR #45 as well. It was resubmitted before I corrected the description in the updated recorder. I will fix the description and submit once more.
Hi team, what is the exact closing time and time zone for our project submission today
Hi! I asked a few participants who have already submitted their apps, and I found that the people using v1.3.16 were able to use the Record button successfully, while some people on v1.3.18 were experiencing recording issues.
In my case, I initially saw the Record button on an older version, but the recording itself wasn't working. After the team mentioned that the recording issue was fixed in a newer release, I updated my Docker setup. However, after updating, the Record button itself disappeared.
I've since tried v1.3.16, v1.3.18, and the newer version again, but I still can't get the Record button to appear. I've also tried recreating the containers and reusing my existing volumes.
Could this be related to some persisted configuration, feature flag, or frontend state in my Docker volumes? Is there a recommended clean upgrade path or configuration I should follow to restore the Record button?
π1
7 replies
@user @user It's nice to participate in this hackathon, however, for me, and I guess for many others too, it's more of "navigating" the platform & co, and getting the model to responded as "expected" than actually fine-tuning your app swag. So in a nut shell, it's been platform-centric rather than on app-centricπ
i had done with my submission but the app was not in gallery
Last day of the Hackathon :unicorn_face:
Dear participants, you have 14 hours left to submit your apps! Submissions close today, July 29, at 23:59 UTC.
Donβt forget to enter the Community Buzz category: share your app online, include a link to it, and tag us so we can see your post.
:runner:1
1 reply
I've finished building the app, but I'm confused about the submission process. The brief mentions a recording and submission option available within the chat/app interface, but I can't locate it anywhere in the Archestra UI (checked the app view, the "..." menu, and sidebar). Could you point me to where this recording/submission feature is, or clarify whether I should instead record my screen externally (e.g., via Xbox Game Bar/OBS) and submit the video link separately?
Read-only live mirror of Archestra.AI Slack
πJoin the discussion withAI enthusiasts!Hi! I asked a few participants who have already submitted their apps, and I found that the people using v1.3.16 were able to use the Record button successfully, while some people on v1.3.18 were experiencing recording issues.
In my case, I initially saw the Record button on an older version, but the recording itself wasn't working. After the team mentioned that the recording issue was fixed in a newer release, I updated my Docker setup. However, after updating, the Record button itself disappeared.
I've since tried v1.3.16, v1.3.18, and the newer version again, but I still can't get the Record button to appear. I've also tried recreating the containers and reusing my existing volumes.
Could this be related to some persisted configuration, feature flag, or frontend state in my Docker volumes? Is there a recommended clean upgrade path or configuration I should follow to restore the Record button?
π1
7 replies
Let me check the GitHub repo for any recent changes or issues related to the Record button and version differences. I don't have access to tools to check the repo directly right now. Based on your description: *Likely cause: The Record button visibility is controlled by a feature flag or setting that got persisted in your Docker volumes during the upgrade. Clean upgrade path to try: 1. Full volume reset (cleanest): ``
bash docker compose down -v docker compose pull docker compose up -d `` This removes all volumes and starts fresh on v1.3.19 (the latest shown in your screenshot). 2. If you need to preserve data, try clearing just the frontend/config-related volumes while keeping your core data. 3. Check browser:* Also try hard refresh (Ctrl+Shift+R) or incognito mode to rule out browser caching. Your screenshot shows v1.3.16 with v1.3.19 available β I'd recommend doing a clean upgrade to v1.3.19 with the volume reset above. The team has been actively fixing recording issues in recent releases. Want me to flag this to the team for a more definitive answer on which specific volume might be caching the feature flag? π€ Slack Agent:mute:1
Replied in dm
Solved
Awesome, glad it's sorted! π π€ Slack Agent
mute
:mute: Roger that, I'll hush up β @mention me to bring me back.
Heads up :mega: For anyone experiencing missing :blackrightpointingtrianglewithdoubleverticalbar: hackathon recorder, please add `-e ARCHESTRAHACKATHONRECORDERENTERPRISE_OVERRIDE=true
env var arg to your π³ docker run` command from the quickstart guide. Thank you π