We are encountering this much more frequency in recent weeks.
A user installs our app initially in Workspace A (the default now seems to be restrict to a single workspace for some accounts). Then on a board in Workspace B, the app is visible and an integration recipe can be created - but the app does not have access to Workspace B.
Logic would dictate that the app should not be visible when adding integrations to boards in Workspace B. However, that doesn’t appear to be true, and the recipe gets installed. To add to it, the recipe triggers and sends us an event as if everything works.
However, the token we receive cannot read or write anything to that board (it can access users, account, etc.). This means the integration is failing.
We had not seen this regularly until the last couple weeks - did something change recently that allows the app to be visible for use in a workspace it does not have access to?
Lastly, I would say this is a bug, an app should not be visible to create recipes in a workspace it won’t function in, nor should any triggered events from such a workspace (say access to the workspace was later removed) be sent.