You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Reference
Based on this Large Scale Notification GitHub repository
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:
Has anyone tried on this issue?
Thank you.
The text was updated successfully, but these errors were encountered: