Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure
TypeScript
docs(teams): correct the account-linking path and document the install that works
Jose Ramirez505d47c0bcd5
diff --git a/control-ui/app/communication-channels/new/page.tsx b/control-ui/app/communication-channels/new/page.tsxindex faff526be..739ae65f5 100644--- a/control-ui/app/communication-channels/new/page.tsx+++ b/control-ui/app/communication-channels/new/page.tsx@@ -872,17 +872,19 @@ export default function CreateCommunicationChannelPage() {Install in Teams</a><p className="cu-teams-setup__install-note">- Teams can take around five minutes to publish the app to its- catalog, so the link may say the app cannot be found at first.- That is the expected wait, not a broken setup: give it a couple of- minutes and click it again.+ A newly created app is not in the Teams catalog yet, so this link+ may say the app cannot be found. That is expected, not a broken+ setup, and re-running the create command would leave you with two+ bots. The wait is open ended, so to install now, upload the+ package instead.</p><details className="cu-advanced-details cu-teams-setup__fallback">- <summary>If it still fails after several minutes</summary>+ <summary>Install now by uploading the package</summary><p className="cu-advanced-details__hint">- Build the package and upload it by hand from Apps > Manage- your apps > Upload an app. This skips the catalog lookup that- the link depends on.+ This sideloads the app without waiting on the catalog. Run the+ command, then in Teams choose Apps > Manage your apps >+ Upload an app > Upload a custom app, and pick the channel+ during install.</p><CommandBlockcommand={teamsPackageDownloadCommand}diff --git a/control-ui/components/__tests__/CreateCommunicationChannelPage.test.tsx b/control-ui/components/__tests__/CreateCommunicationChannelPage.test.tsxindex cfb62c523..8dca56e63 100644--- a/control-ui/components/__tests__/CreateCommunicationChannelPage.test.tsx+++ b/control-ui/components/__tests__/CreateCommunicationChannelPage.test.tsx@@ -945,7 +945,7 @@ describe('CreateCommunicationChannelPage — Teams install link', () => {expect(disclosure).not.toBeNull()expect(disclosure).not.toHaveAttribute('open')expect(- within(disclosure as HTMLElement).getByText('If it still fails after several minutes')+ within(disclosure as HTMLElement).getByText('Install now by uploading the package')).toBeInTheDocument()})@@ -972,7 +972,7 @@ describe('CreateCommunicationChannelPage — Teams install link', () => {// this reaches the operator AFTER they have read "app cannot be found" as a// broken setup and started debugging the wrong thing. It has to be visible// before the click, so it must not sit inside the disclosure.- const note = screen.getByText(/five minutes to publish the app to its catalog/)+ const note = screen.getByText(/not in the Teams catalog yet/)expect(note.closest('details')).toBeNull()})})diff --git a/docs/how-to/connect-teams.md b/docs/how-to/connect-teams.mdindex 2973c2add..f047304aa 100644--- a/docs/how-to/connect-teams.md+++ b/docs/how-to/connect-teams.md@@ -203,12 +203,25 @@ or a screenshot.Open the install link, add the app, and optionally add it to a channel.-**Expect to wait about five minutes.** Teams publishes the app to its catalog on-its own schedule, and the install link fails with "This app cannot be found"-until that finishes. That is the normal wait, not a broken setup, and it is not-a reason to re-run `teams app create`, which would leave you with two bots. Give-it a couple of minutes and click the link again. Only if it still fails after-several minutes is something actually wrong: see Troubleshooting.+**A freshly created app is not in the catalog yet.** Teams publishes it on its+own schedule, and until that finishes the install link returns "This app cannot+be found". That is not a broken setup, and it is not a reason to re-run+`teams app create`, which would leave you with two bots. Observed on this+platform: the link failed on an app 22 minutes old and worked on one two days+old, so treat the wait as open-ended rather than a fixed number of minutes.++**To install now, upload the package instead.** This sideloads the app directly+and does not wait on the catalog, which makes it the reliable path on a+just-created app:++```shell+teams app package download YOUR_CLIENT_ID+```++Then in Teams: **Apps > Manage your apps > Upload an app > Upload a custom+app**, pick the generated `.zip`, and choose the channel during install rather+than adding it afterwards. Build the package _after_ the `supportsFiles` update+above, so the uploaded manifest already carries it.## Any cluster (CRD path)@@ -253,7 +266,9 @@ spec:**Do this before trying to chat.** Until a conversation is confirmed, the agentwill not act on it.-1. Open **Profile UI > Settings > Approval Channels > Teams**.+1. Open **Profile UI > Settings > Social channels > Teams** and choose+ **Connect Microsoft Teams**. This is a tab under **Settings**, not the+ **Approval Channels** page in the sidebar, which is a different screen.2. Start a connection and pick the Teams channel.3. Copy the code it shows.4. Open the conversation you want to connect. For a channel, add the bot to it@@ -312,14 +327,19 @@ returns this even though the app exists and is visible in the Developer Portal.It reads like the create failed. It did not: re-running `teams app create` inresponse leaves you with two bots.-For roughly the first five minutes this is just the catalog catching up, and the-fix is to wait and click the link again. Everything below is for a link that is-still failing after several minutes.+This is the catalog catching up, and waiting does eventually clear it, but the+wait is open-ended: observed failing on an app 22 minutes old and working on one+two days old. Do not plan around a number.++Three ways past it, most reliable first:-Two workarounds. Use **Preview in Teams** from the-[Developer Portal](https://dev.teams.microsoft.com/apps) instead of the-printed link; it bypasses the catalog lookup that is failing. Or regenerate the-link:+1. **Upload the package** (see "Install the app in Teams" above). This sideloads+ the app and never consults the catalog, so it works on an app created+ seconds ago.+2. Use **Preview in Teams** from the+ [Developer Portal](https://dev.teams.microsoft.com/apps) instead of the+ printed link; it also bypasses the catalog lookup.+3. Wait, then regenerate the link and try again:```shellteams app get YOUR_CLIENT_ID --install-link