Event triggered by unknown workspace

[kronosapiens]

@slack/bolt version

^3.17.0

Your App and Receiver Configuration

const app = new App({
  logLevel: LogLevel.WARN,
  signingSecret: process.env.CHORES_SIGNING_SECRET,
  clientId: process.env.CHORES_CLIENT_ID,
  clientSecret: process.env.CHORES_CLIENT_SECRET,
  stateSecret: process.env.STATE_SECRET,
  customRoutes: [ common.homeEndpoint('Chores') ],
  scopes: [
    'channels:history',
    'channels:join',
    'chat:write',
    'commands',
    'groups:history',
    'users:read',
  ],
  installationStore: {
    storeInstallation: async (installation) => {
      await Admin.addHouse(installation.team.id, installation.team.name); # team_id stored in the DB
      await Admin.updateHouseConf(installation.team.id, CHORES_CONF, { oauth: installation });
      console.log(`chores installed @ ${installation.team.id}`);
    },
    fetchInstallation: async (installQuery) => {
      ({ choresConf } = (await Admin.getHouse(installQuery.teamId)));
      return choresConf.oauth;
    },
    deleteInstallation: async (installQuery) => {
      await Admin.updateHouseConf(installQuery.teamId, CHORES_CONF, { oauth: null });
      console.log(`chores uninstalled @ ${installQuery.teamId}`);
    },
  },
  installerOptions: { directInstall: true },
});

Node.js runtime version

^20.11.0

More information:

Original issue here.

I am seeing the following error in my logs:

chores user_change

[ERROR]  bolt-app error: insert into "Resident" ("activeAt", "exemptAt", "houseId", "slackId") values ($1, $2, $3, $4)
  detail: 'Key (houseId)=(E011XGDUJMC) is not present in table "House".', 

This is caused by the app receiving the user_change event for a workspace (E011XGDUJMC) which is not stored in the database. This is surprising, as it is unclear why the app is receiving an event from a workspace which has never installed the app. The main clue is the leading character of the identifier - E - suggests that this is not a typical workspace. Perhaps this is some feature of Enterprise which I am unaware of?

Would be curious to resolve the issue. Thanks!

[hello-ashleyintech]

Hi, @kronosapiens! 👋 Thanks for submitting this issue!

Based on the description provided, it sounds like your issue could be due to grid migration. I would recommend using one of (or even better, both!) of the following approaches:

• Use the auth.test API to maintain the enterprise_id / team_id in your installation store database
• Detect the migration event using the Events API

I hope this helps - let me know if you have further questions! 😄

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[github-actions]

As this issue has been inactive for more than one month, we will be closing it. Thank you to all the participants! If you would like to raise a related issue, please create a new issue which includes your specific details and references this issue number.