v1.4.1

v1.4.1

A follow-up to v1.4.0. This release fixes two problems with @poll and @retry: polling timeouts could discard the response, and polling or retrying time was missing from @compare rows and workflow steps.

Fixed

Polling timeouts keep the last completed response

When @poll reached its timeout while a request was still in flight, Resterm returned that unfinished request instead of the last real response from the server. The response pane said last response shown but showed nothing, the status code was missing, and history recorded an entry with status 0 and an empty body.

### Wait for a job to finish
# @poll every=500ms timeout=30s until=response.json().status == "completed"
GET {{base.url}}/jobs/{{job.id}}

• If at least one attempt completed, Resterm now shows the last completed response when the timeout is reached.
• If no attempt completed, Resterm reports the polling timeout without presenting an empty server response.
• History no longer records these timeouts as responses with status 0 and an empty body.

Polling and retry time is included in comparisons and workflows

• @compare rows and workflow steps now report the full elapsed request time, including waits between polling or retry attempts.
• Compare totals stored in history now use the same full duration.
• These durations also include pre-request and response scripts, so they may be slightly higher even without @poll or @retry.
• The response pane is unchanged: it still reports the transport time of a single response.