AGENT SKILL

okta-workflows-tables

Use when working with Okta Workflows Tables (the built-in data store): Search Rows (searchRows2) being case-sensitive ('The search expression is case sensitive') with no 'starts with' for text; the hard 3,500-row return cap regardless of the Limit field (page with the 0-based Offset input); table hard limits (500,000 rows/table, 64 columns/table, 16 KB / 16,000 chars per cell, 200 tables paid / 100 free); the Where Expression JSON lhs/op/join/rhs quirk when testing with variables; the no-native-upsert read-then-write race (Search Rows → If/Else on Row ID empty → Create Row or Update Row, duplicate rows under concurrency, serialize with a concurrency=1 helper — labeled THEORY); and high-frequency table requests triggering throttling. Triggers on Search Rows, searchRows2, case-sensitive table search, 3500 rows, Offset pagination, Where Expression, upsert, Create Row / Update Row race, table row/column/cell limits, To Lower Case.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 5
Forks
3

01 前言 Front Matter

name
okta-workflows-tables
description
Use when working with Okta Workflows Tables (the built-in data store): Search Rows (searchRows2) being case-sensitive ('The search expression is case sensitive') with no 'starts with' for text; the hard 3,500-row return cap regardless of the Limit field (page with the 0-based Offset input); table hard limits (500,000 rows/table, 64 columns/table, 16 KB / 16,000 chars per cell, 200 tables paid / 100 free); the Where Expression JSON lhs/op/join/rhs quirk when testing with variables; the no-native-upsert read-then-write race (Search Rows → If/Else on Row ID empty → Create Row or Update Row, duplicate rows under concurrency, serialize with a concurrency=1 helper — labeled THEORY); and high-frequency table requests triggering throttling. Triggers on Search Rows, searchRows2, case-sensitive table search, 3500 rows, Offset pagination, Where Expression, upsert, Create Row / Update Row race, table row/column/cell limits, To Lower Case.

03 SKILL.md 正文

Okta Workflows — Tables (Built-in Data Store) (§3)

Six quirks. Normalize case before writing AND searching, and never assume Search Rows returns more than 3,500 rows.

Quirk 3.1 — Search Rows (searchRows2) is case-sensitive

The Search Rows card documentation states plainly: "The search expression is case sensitive." Numeric conditions are fine; text matching fails on case mismatch, and there is no "starts with" for text.

  • Workaround: Normalize case with a Text - To Lower Case card before writing AND before searching, or pull all rows and use a List - Filter (Custom) helper flow to perform case-insensitive/starts-with matching.
  • Sources: Okta docs stash_searchrows2.htm; support.okta.com searching-a-table-using-a-custom-filter-in-workflows; maxkatz.net 2024/01/19

Quirk 3.2 — Hard 3,500-row return cap regardless of Limit

"Regardless of the limit selected, the function card returns a maximum of 3,500 rows from the selected table" (stash_searchrows2.htm). Confirmed independently by Max Katz "Workflows Tips #36" (maxkatz.net, 2022/09/09): "If a filter or limit is not applied to the table search, a maximum of 3,500 rows from the selected table will be read by the Search Rows function card." Critical for sync-reconciliation tables that can grow large.

  • Workaround: Page with the Offset input (0-based) in a recursive/paginated helper flow, or design tables to be queried by indexed key columns returning fewer than 3,500 rows.

Quirk 3.3 — Table hard limits

500,000 rows/table; 64 columns/table; 16 KB (16,000 chars) per cell; 200 tables (paid) / 100 (free). "You can't add a row to a table after you've reached the limit."

  • Source: workflows-system-limits.htm

Quirk 3.4 — Where Expression JSON quirk when testing with variables

When passing a variable into the Where Expression and testing the card, you must hand-edit the Where Expression JSON (lhs/op/join/rhs structure) or the test returns wrong output. Example: {"expr":[{"lhs":"Country","op":"=","join":"AND","rhs":"Brazil"},{"lhs":"Code","op":"=","join":"AND","rhs":"BR"}]}.

Quirk 3.5 — No native upsert / concurrent-write race risk (THEORY)

There is no atomic upsert; the documented pattern is Search Rows → If/Else on Row ID empty → Create Row or Update Row. When multiple concurrent flow executions (e.g., many event-hook-triggered flows) run this read-then-write against the same table/key, there is a classic race window that can create duplicate rows. This concurrency/locking risk is a plausible-but-not-explicitly-documented inference from the read-then-write pattern — label as THEORY. Mitigation: funnel all table writes through a single-concurrency (concurrency=1) helper flow or a scheduled batch to serialize writes.

Quirk 3.6 — High-frequency table requests trigger throttling

"Table requests" is an explicit throttling resource: "Flows with highly active event cards that make requests through Tables function cards" are called out as throttling-eligible.

  • Source: about-execution-limits.htm

04 同仓库更多 Skills

the-vibey-project
the-vibey-project/vibey

white-paper-writing

Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks "how should I structure this" for a long-form document.

★ 5
the-vibey-project
the-vibey-project/vibey

prose-technical-mechanics

Use when editing or writing prose at a technical/mechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.

★ 5
the-vibey-project
the-vibey-project/vibey

prose-mechanics

Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate/Jamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix "AI-sounding" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.

★ 5
the-vibey-project
the-vibey-project/vibey

narrative-structure

Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or "how should I structure this story/pitch/presentation" request.

★ 5
the-vibey-project
the-vibey-project/vibey

legal-brief-writing

Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic/neurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.

★ 5
the-vibey-project
the-vibey-project/vibey

journal-publishability-criteria

Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs/paper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.

★ 5