insomnia
insomnia copied to clipboard
Query parameters randomly getting lost
Expected Behavior
Adding a new Query parameter (name and value) and sending the request should work.
Actual Behavior
Query parameter name or value randomly getting lost or reset. Sometimes one or many Query parameters name and or value field are empy, reset to a previous value or text getting cut after sending the request.
Reproduction Steps
It seems to be related to the number of folders and or requests in a collection. Only started happening in a bigger project with over a hundred requests.
Could kind of reproduce it by creating a new project. Create a folder. Add another folder inside of the top folder and add like ten requests each with around ten query parameters to it. Duplicate the folder with those requests like 10 times. After that just pick one request and add another parameter. Send the request. Do that a few times and the issue should start appearing.
Is there an existing issue for this?
- [X] I have searched the issue tracker for this problem.
Additional Information
I am pretty sure this did not happen a few weeks ago.
Insomnia Version
2023.5.7
What operating system are you using?
Windows
Operating System Version
Windows 10
Installation method
Download from Insomnia website
Last Known Working Insomnia version
No response
Not sure if 100% related:
Can confirm that it happens if you specify the query string in the URL bar, as opposed to in the query parameter tab. I can make it happen by doing it as follows:
- Make a call to
http://localhost:5000/v1/feed?page=1
- Change the URL to
http://localhost:5000/v1/feed?page=2
, press enter ASAP - The timeline mentions that
http://localhost:5000/v1/feed?page=1
is called, or it callshttp://localhost:5000/v1/feed?page=
. Presumably, that is what was captured when I pressed backspace to do it.
If I leave a second between each call (I found it while crawling an API), it doesn't seem to happen. Same for using the query tab. This is an okay workaround for me.
I can back this bug up, and can also confirm it still happens when using the QUERY PARAMETERS
tab.
This is before sending the request:
And this is what's left after the request is sent