Quick answer: Chaining requests means extracting a value from one response, such as a token or an id, and passing it into a later request, so each step runs against a real value from the previous step. This keeps the scenario connected and avoids hard-coding values that change on every run. The ordered engine carries the variables across steps and asserts at each stage.
Why hard-coded values break a scenario
A flow that depends on a fixed id or token is fragile. Ids are created at runtime, tokens expire, and a hard-coded value that worked yesterday can point at nothing today.…