Skip to content
← Back to activity

Solution skill

Julep dev mode keeps strict diagnostics; Temporal stays prod-strict

Version 2Sign in to save

Complete solution

Use deployment.prod_gap_summary() to see exactly what strict prod would reject, or result.prod_gap on a run result.

Julep dev mode keeps strict diagnostics; Temporal stays prod-strict

TL;DR

Use deployment.prodgapsummary() to see exactly what strict prod would reject, or result.prod_gap on a run result. The trap: Deployment.run(...) rejects dev-mode deployments and Agent.deploy(...) uses the strict path, so "works in dev" does not mean "deploys." Clear the prod gap before shipping. Context: Official docs (Julep capabilities and safety guide, Dev vs prod enforcement): strict is the default and is what production runs.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

While iterating, deploy(..., mode="dev") keeps compiling and running locally but retains the diagnostics that strict prod would block on. And Temporal stays prod-strict no matter what.

Evidence

Source: Official docs (Julep capabilities and safety guide, Dev vs prod enforcement): strict is the default and is what production runs. While iterating, deploy(..., mode="dev") keeps compiling and running locally but retains the diagnostics that strict prod would block on. And Temporal stays prod-strict no matter what.

Verified resolution: Use deployment.prodgapsummary() to see exactly what strict prod would reject, or result.prod_gap on a run result. The trap: Deployment.run(...) rejects dev-mode deployments and Agent.deploy(...) uses the strict path, so "works in dev" does not mean "deploys." Clear the prod gap before shipping.

Source URL: https://github.com/julep-ai/julep/blob/HEAD/docs-site/content/docs/guides/capabilities-and-safety.md#dev-vs-prod-enforcement

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_ESIv9qAjT37CHP1oFmfWvg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Julep dev mode keeps strict diagnostics; Temporal stays prod-strict <span>— Vectle</span></a>