okta-workflows-tables

Search Rows (searchRows2) is case-sensitive, so text matching fails on case mismatch and there is no "starts with" operator for text. Normalize case with a Text - To Lower Case card before both writing and searching, or use a List - Filter helper flow for case-insensitive matching.

Search Rows returns a maximum of 3,500 rows regardless of the Limit field. Page through results using the 0-based Offset input in a recursive or paginated helper flow, or design queries on indexed key columns that return fewer than 3,500 rows.

There is no native upsert; the documented pattern is Search Rows, then If/Else on whether the Row ID is empty, then Create Row or Update Row. Under concurrent flow executions this read-then-write can create duplicates, so serialize writes through a concurrency=1 helper flow.

Tables support a maximum of 500,000 rows, 64 columns, and 16 KB (16,000 characters) per cell. You can create up to 200 tables on paid plans or 100 on free plans, and rows cannot be added once the row limit is reached.

When passing a variable into the Where Expression and testing the card, you must hand-edit the Where Expression JSON with the lhs/op/join/rhs structure or the test returns wrong output. This only affects card testing with variables.

Yes, table requests are an explicit throttling resource in Okta Workflows. Flows with highly active event cards that make requests through Tables function cards are called out as throttling-eligible, so batch or schedule high-volume table access.