Timeinator has been working flawlessy a few weeks ago, but is now showing an unexpected behaviour: Each run gets stuck at exactly 50% progress.
Logger++ reveals that requests are being properly sent by the extension, yet only for the very first payload. Subsequent payloads are being ignored. The intended timing analysis is hence impossible.
Observed this behaviour on different OS's, e.g. Win 10 and MacOS. Currently on Burp Pro v2022.8.2.
Let me know if I can help with more debug info to track this down.