Multistep workflow failing

[AmritSDutta]

Name: upstash-workflow
Version: 0.1.3

2nd step is always failing.

File "/usr/local/lib/python3.11/site-packages/upstash_workflow/asyncio/serve/serve.py", line 166, in _safe_handler
return await _handler(request)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/upstash_workflow/asyncio/serve/serve.py", line 91, in _handler
parse_request_response = _parse_request(request_payload, is_first_invocation)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/upstash_workflow/workflow_parser.py", line 182, in _parse_request
raw_initial_payload, steps = _parse_payload(request_payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/upstash_workflow/workflow_parser.py", line 67, in _parse_payload
raw_initial_payload = _decode_base64(encoded_initial_payload["body"])
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
TypeError: string indices must be integers, not 'str'

[CahidArda]

Thanks for the report, and apologies for the slow response.

Root cause: qstash-py 3.0 changed prepare_headers to prefix every header with Upstash-Forward- (2.x left upstash-* headers untouched). upstash-workflow passed its workflow control headers (Upstash-Workflow-Init, -RunId, -Url, Upstash-Feature-Set, …) through publish_json, so they arrived at QStash as ordinary forwarded headers. QStash then didn't recognize the request as a workflow start and called the endpoint with the raw body plus a forwarded Upstash-Workflow-Sdk-Version header — the SDK treated that as a step request, tried to parse a JSON object as the step array, and crashed in _parse_payload with the TypeError in your traceback. This reproduces on 0.1.3 whenever qstash 3.x is installed (0.1.3 pins qstash<3, so it needed a manual pip install -U qstash), and would have affected everyone once the SDK moved to qstash 3.

Fix: #44 — the first invocation and context.call results now go through the raw HTTP client with headers untouched, mirroring workflow-js (/v2/batch for the trigger, /v2/publish for call results). Along the way we also fixed the first-invocation message missing its failure callback (so failure_function now fires for first-step failures) and context.call returning a raw dict for non-JSON responses.

Released in v2.0.0 (pip install --upgrade upstash-workflow; requires qstash>=3.4, major bump because of that dependency change). Verified end-to-end against the local QStash dev server with run/sleep/sleep_until/call/failure callbacks on both the FastAPI and Flask integrations.

Closing — please reopen if you still see this after upgrading.