Skip to content

Commit 24606c6

Browse files
authored
Add a note that orchestrator return value has to be natively serializable
1 parent b2baea3 commit 24606c6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/durable/durable-functions-serialization-and-persistence.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ For full customization of the serialization/deserialization pipeline, consider h
155155

156156
It's recommended to use type annotations to ensure Durable Functions serializes and deserializes your data correctly. While many built-in types are handled automatically, some built-in data types require type annotations to preserve the type during deserialization.
157157

158-
For custom data types, you make JSON serialization and deserialization possible by defining class methods `to_json` and `from_json` on your data type class.
158+
For custom data types, you make JSON serialization and deserialization possible by defining class methods `to_json` and `from_json` on your data type class. Note that these methods are not called on the return value from the orchestrator function, meaning the return value has to be natively JSON-serializable. For more information, see [Bindings](durable-functions-bindings.md#python-trigger-usage).
159159

160160
# [Java](#tab/java)
161161

0 commit comments

Comments
 (0)