HistoryCountLimitError and HistoryLimitWarn configuration in Python

[ammar-deriv]

---

History total size limit (leading to a terminated Workflow Execution):

• • Temporal warns at 10 MB: history size exceeds warn limit.

  • Temporal errors at 50 MB: history size exceeds error limit.

  • This is configurable with HistorySizeLimitError and HistorySizeLimitWarn.

• History total count limit (leading to a terminated Workflow Execution):

  • Temporal warns after 10,240 Events: history size exceeds warn limit.

  • Temporal errors after 51,200 Events: history size exceeds error limit.

  • This is configurable with HistoryCountLimitError and HistoryCountLimitWarn.

---

I am using Python SDK to develop my ETL. I did not found any part where I can configure the HistoryCountLimitError and HistoryLimitWarn in Python.

Is this really configurable?

Appreciate anyone can clarify this things? Thanks.

[antonio.perez]

Hi,

it is a server config

You can use the following keys in the dynamic config to overwrite the values

• temporal/common/dynamicconfig/constants.go at 1dc6264f4f9372a9437383408c230c950bfb26a5 · temporalio/temporal · GitHub
• temporal/common/dynamicconfig/constants.go at 1dc6264f4f9372a9437383408c230c950bfb26a5 · temporalio/temporal · GitHub

eg:

limit.historySize.error:
  - value: 134217728

I would consider other approaches like storing the payload in an external data-store and passing the reference instead, then from your activity you can run a query to retrieve the data.

[ammar-deriv]

omg please include this in the docs. i thought the limitation is very strict. does the implementation for Python is also the same? or I need to use Go syntax too to overwrite this? or do i need to patch it by myself in the package? @antonio.perez

[antonio.perez]

The dynamic config is for the Temporal Server (not for the sdk)

[ammar-deriv]

Yeah, but the link that you gave is for Go config. What about other language Config? But nevermind, I found the YAML config. Docs so bad.