This message in the Discord gave me the idea for this. Credit to Magic lol.
Since Inventor is what is retrying stuff, it would be cool if it had a list (perhaps on the errors page?) of what actions are queued, when it will retry, what flow, etc.
This message in the Discord gave me the idea for this. Credit to Magic lol.
Since Inventor is what is retrying stuff, it would be cool if it had a list (perhaps on the errors page?) of what actions are queued, when it will retry, what flow, etc.
There are technical reasons preventing this data from being easily be exposed to end-users.
Ratelimit data is all stored in-memory and we avoid locking access as much as possible to keep it fast. Allowing external viewing/access would require either replicating that data to a DB (making both reads and writes slower) or locking the in-memory object for display on a page (delaying access).
Internal telemetry only collects minimally-detailed summaries on a sample of ratelimits and locks in order to prevent broad performance impacts, trying to create fully-detailed and real-time updated logs would cause a lot of problems.