In the app: Help

Help

Help collects the pages that cut across every area: how long-running work runs in the background, where AI assists you, reference tables, answers to common questions, and fixes for common problems.

Background jobs

What runs in the background Imports, AI generation, Pipeline procedures, ontology sync, and other long work run as background jobs on the server. Here’s what they are and why. Where to watch background jobs Follow long-running work from the Background Jobs and Schema Imports tabs, the Home page’s In progress card, or the screen where you started it. Read a background job's status What each job state means, how to read the progress bar and Message column, and how schema imports report their phases. Cancel a running job Which background jobs you can stop, where the cancel control is for each, and what happens to work that already finished. Recover from a failed job Find out why a background job failed, fix the cause for each kind of job, and decide when to escalate. Background job kinds The job names you’ll see on the Background Jobs tab, what each one does, and where it’s started.

AI assistance

Where AI helps in Kenseme Every AI feature in Kenseme, grouped by where you’ll find it in the app, with a link to the page that explains each one. Reviewing AI suggestions The four ways Kenseme puts AI output in front of you (inline suggestions, review lists, proposal cards, and undoable edits) and how to judge what to keep.

Reference

Kenseme glossary Plain definitions of the words Kenseme uses, from ontology, binding, and lakehouse to Pipeline, star schema, Data Agent, and seat.

FAQ

FAQ: signing in and organizations Quick answers for your first day: signing in, verifying your email, invitations, organizations, your profile and the theme. FAQ: plans and billing Quick answers about trials, AI usage, seats, changing or cancelling your plan, failed payments and who can see billing. FAQ: schema importing Answers about script and connection imports: file types, size limits, timing, existing objects, enums, descriptions and failures. FAQ: SQL generation and versions Answers about version scripts, migration scripts, dialects, notebooks, AI validation, and the z_blaze_version table. FAQ: Pipelines Quick answers about Pipeline statuses, load strategies, finalizing, generating and running load code, drift, and rollback. FAQ: Industry Standards Answers about Standards access, who can enable standards, search coverage, summaries, FIBO modules, exact vs agent-generated imports, and partial imports. FAQ: AI assistance Quick answers about what the AI sees, whether it touches your databases, how it counts against your allowance, and what to do when a suggestion is wrong. FAQ: background jobs Quick answers about where background jobs appear, what their states mean, how long they’re listed, and what to do when one is stuck or failed.

Troubleshooting

Troubleshooting: my schema import is stuck or failing Symptoms by stage (splitting, tables, indexes, relationships, SQL objects, descriptions) and for connection imports, with what to do about each. Troubleshooting: the fix-import dialog didn't help What to do when the Fix & Retry explanation is vague, your edit didn’t work, a dependency is missing, or you want to give up on an item. Troubleshooting: generated SQL fails on the target database What to check when a generated version or migration script fails: dialect mismatches, skipped objects, permissions, defaults, keys, and re-runs. Troubleshooting: a generated notebook fails on Databricks or Fabric Lakehouse What to check when a Kenseme-generated notebook fails: materialized view requirements, missing schemas, permissions, commented-out cells, and zero-row loads. Troubleshooting: my Pipeline will not validate Fixes for each Pipeline validation error and warning, from missing keys and duplicate names to stale mappings and text columns without a length. Troubleshooting: my Pipeline procedure will not generate What to check when a load procedure or PySpark function fails to generate, preview, or appear in the destination schema. Troubleshooting a background job What to check when a background job won’t start, stops moving, fails, or doesn’t appear, and what to send when you escalate.