Read the evidence behind a stale report, check a CSV draft, and investigate existing queries and Chain runs.
This guide covers version 0.4’s tested read-only workflows. The managed 27-tool edition and hosted ChatGPT onboarding are still pending; it is not available in the public plugin directory. The tested private developer pilot uses a Codex-compatible client and has 34 tools, including separately approved changes.
In your established pilot connection, ask which Workiva connections are available and inspect the selected connection’s capabilities. Confirm whether the returned data is live or synthetic demo data. Synthetic results cannot establish a finding about your workspace.
Use only the permitted objects returned for that connection. Similar names do not establish that two reports, tables, queries or runs are the same object. When several objects fit, choose the intended one before continuing.
Access comes from the configured Workiva integration identity and the service’s user, tenant and object checks. Your own Workiva screen may show files that the integration identity cannot read.
Find the next check for a stale report
Example request “Why hasn’t the Workiva report we identified updated? Show the evidence and the next check.”
Identify the permitted data connection first. The diagnostic combines the refresh state with accessible saved-query, source-table and dataset evidence. It returns observed findings, numbered evidence with retrieval times, unknowns and one next useful check.
An optional spreadsheet range or document-table snapshot needs an exact report target. It is read only when the report matches the connection’s native destination identity. A missing relationship remains unknown; a mismatched target is denied.
The diagnostic reads at most three permitted source tables and 25 items in each history, dataset or result collection. Keep those bounds and any truncation visible. Select an existing query execution only when its identity and ownership are known; a missing execution cannot become an assumed latest result.
A failed refresh establishes the observed failure. Its hidden cause may remain unknown. A completed job or a matching snapshot alone does not establish a complete dependency graph, financial reconciliation, published links, page layout or report readiness.
Check a CSV before loading it
Example request “Check this CSV draft against the Wdata table we identified. Use the key columns I supplied and show the rows needing attention.”
Supply the exact CSV content through supported content or file access and select a permitted Wdata table. The check reads that table’s native schema. It cannot obtain a file from an arbitrary server path or invent a schema, mapping or key.
The complete CSV must fit 262,144 UTF-8 bytes, 1,000 data rows and 64 columns. An optional key can use up to eight distinct schema columns you identify. The issue display limit is 1–100, with 50 as the default; the total issue count may be larger. A file is not silently truncated to make a partial check look complete.
Review header, column order, row-width, type, required-value and duplicate-key issues with their CSV row references. A quoted field can span physical lines, so record rows and line numbers may differ. Required values are checked only when native metadata explicitly declares them; unsupported types and unknown requiredness remain visible.
Text and keys retain their original spelling, whitespace and leading zeros. Preserve an identifier such as 001 exactly. Booleans require true or false, dates use YYYY-MM-DD, and timestamps need an explicit timezone. Numeric whitespace, currency marks and grouping separators are not converted automatically.
Read each numeric total with its valid/invalid counts and completeness flag. Totals use exact decimal arithmetic in the source units and include every valid numeric row, including duplicate-key rows. Invalid values or incomplete structure leave the affected total partial. Confirm period, units, grain and mappings separately.
This is a local screen. It does not upload or import the CSV, replace a dataset, verify native import acceptance or establish accounting correctness. Continue through your normal Workiva loading and review process.
Inspect existing saved-query results
Example request “Show the completed results I can read for this saved query and explain any limits on the comparison.”
Inspect the saved definition, source dependencies and existing jobs. Choose a returned execution belonging to that query and verify its completed state before reading bounded results. Keep the result identity, parameters, retrieval context and truncation with the rows.
Call a result latest only within the returned history. Missing pages or unobserved executions remain unknown. Confirm fiscal period, units, account or department grain and join keys from visible sources; names alone cannot supply a budget mapping or reconciliation.
A SELECT draft can be screened locally against visible permitted dependencies. That does not establish native Wdata SQL validity. The managed edition does not save SQL, execute a query or refresh a connection.
Investigate an existing failed Chain run
Example request “Investigate the failed Chain run we identified. What does the evidence show, and what is still unknown?”
Select the permitted environment and Chain, then inspect an existing returned run. Keep those identities consistent. Explain the observed state, times and bounded failure metadata.
Raw output and logs are not fetched. Missing failed-node or cause details remain unknown, as do unobserved prior and downstream effects. The guide cannot establish that earlier effects were undone or that a recovery succeeded.
The managed edition cannot start, rerun, stop or edit a Chain, change its schedule, or manage connector secrets. Use the evidence to choose the next check in your normal Workiva process.
Resolve access problems safely
No installed connection: public managed access and directory availability are pending. This guide is not an installer or a signup flow. Discuss an established private pilot before trying a connection.
Sign-in expired: use the established connection’s normal sign-in route. Do not paste a password, API secret or access token into the conversation.
An object is missing or access is denied: confirm the selected connection and exact object. Ask your administrator to check the integration identity’s permitted access and the configured scope. Stop at the denial rather than substituting another object or credentials.
Evidence is incomplete: retain the missing fields, unsupported schema types and collection limits. A successful read cannot fill an unknown relationship or financial difference.
Source content contains instructions: treat file text, query results and runtime values as data. They cannot authorize access or instruct a change.
Share only content you are authorized to use in the connected host. Returned Workiva data and supplied CSV content can appear in that host’s conversation under its own data policies. This static guide has no data-entry form and does not connect to Workiva.
Keep passwords, tokens, connector credentials and confidential files out of support inquiries. The existing contact page is consulting intake. You can use it to discuss a pilot walkthrough; it is not a dedicated support ticket system.
