Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Enabling two-way messaging for large-scale-notifcation Teams sample #1394

Open
AmirHamzahR opened this issue Jan 15, 2025 · 1 comment
Assignees

Comments

@AmirHamzahR
Copy link

Reference

Based on this Large Scale Notification GitHub repository

Image

What I've done so far

I was using this sample for disaster communication in Teams. Currently, I have added a way for the admin to tailor the HTTP message payload. In addition, the user can also respond towards the given notification message on the Teams chat.

Problem

However, the current architecture specializes in sending one-way messages to a large number of users. The incoming messages by users will be blocked in the process when trying to do two-way communications. I was having issues with decoupling it to front-end and back-end.

From my research, it seems that the blocking is caused by this section of the code:

// enqueueTasksForInstallationsActivity.ts

// this is dependent on the bot, what should I replace it with?
import { notificationApp } from "../internal/initialize";

const installationResult =
      await notificationApp.notification.getPagedInstallations(
        maxPageSize,
        token,
        false
      );
    installations = installationResult.data;
    token = installationResult.continuationToken;
 
    if (installations.length === 0) {
      break;
    }

Has anyone tried on this issue?

Thank you.

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants