Got the same issue as mentionned above

Related to #5930

same here

Related to #5930

It's not the same problem as this one. This problem occurs when importing a collection, for some reason in this latest version if you have a template that uses the response from another request everything will break

+1 on this. We're finding request chaining is broken when importing a collection document.

In our case, we use one request to get a token, and then all subsequent requests retrieve the access token out of the first request's response body.

Recently this seems to have broken, with the request ID failing to match up. It looks like the request ID matches that in the JSON that was imported, so not sure why it's broken.

I've tried "fixing" the reference to the first request, re-exporting, then re-importing, but the collection will be back in a broken state.

Broken reference:

The document that was imported, showing the correct ID:

I would like to add that importing a Collection is imported as a Document instead, which is weird. There is no way to import a Collection, unless you create one first manually and import your data in there. However, you will lose all environments, so yeah import does seem to be very broken.

I get the same behavior. For 2023.2, all requests are given a new request id, even the import file contains ids. The solution for me was to downgrade to 2023.1, import the collection then upgrade to 2023.2. This should be a stable workaround.

This is a PIA. I have to go into the insomnia.Workspace.db file to change the scope from design to collection to have it work as a collection.

Synchronization plugin stop working as well, because of during the import it is always generating new ids for requests/groups )=

I have a similar outcome in the newest version 2023.4.0. Chain requests do not work after import. It works on 2023.1, it does not work on any further version including newest beta version 2023.5

same problem here, with the newest version :( chain requests don't work after import.

I also have problem with import

1. If I imported collection that I previously exported for test purposes (and I have both original and imported collection inside Insomnia even for different projects) values are propagated (still request in GUI empty for imported collection)
   
2. If I remove original collection and I try to use imported one I receive error
   

Looks like elements IDs are propagated between projects and if original collection is unavailable I receiving an error.
Obviously same error if I import collection created by other developers.

Same issue here with latest version.

Me too.
When I import the collection with tags anywhere else, even though the requests exist because they are imported at the same time, the references don't exist because the ids are new.

Any new development here? Still not working in v8.3.0.

Still not working in v8.4.0 :(

Still not working in v8.4.5 :(

Closing as duplicate of #5730