[GH-ISSUE #203] Make refresh event tenant specific #136

Closed
opened 2026-03-03 11:13:20 +03:00 by kerem · 1 comment
Owner

Originally created by @pavanbhaskardev on GitHub (May 30, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/203

Originally assigned to: @pavanbhaskardev on GitHub.

  1. Currently refresh event is not tenant specific
  2. Show when there is a refresh event triggered for a tenant action all other tenants will see the refresh event
  3. End-goal to make the refresh event tenant specific so events won't overlap
Originally created by @pavanbhaskardev on GitHub (May 30, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/203 Originally assigned to: @pavanbhaskardev on GitHub. 1. Currently refresh event is not tenant specific 2. Show when there is a refresh event triggered for a tenant action all other tenants will see the refresh event 3. End-goal to make the refresh event tenant specific so events won't overlap
kerem 2026-03-03 11:13:20 +03:00
Author
Owner

@pavanbhaskardev commented on GitHub (Jul 7, 2025):

  1. Changed the sendEvent logic to tenant specific
  2. Pushed changes to main
<!-- gh-comment-id:3043398140 --> @pavanbhaskardev commented on GitHub (Jul 7, 2025): 1. Changed the sendEvent logic to tenant specific 2. Pushed changes to main
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dflow#136
No description provided.