Dokploy/dokploy · error · Error
No response received from the model
Error message
No response received from the model
What it means
Guard inside createTelegramNotification: after the telegram row insert, the INSERT INTO notifications returned nothing and the whole transaction rolls back — no Telegram destination is persisted.
Source
Thrown at apps/dokploy/server/api/routers/ai.ts:306
z.object({
apiUrl: z.string().min(1),
apiKey: z.string(),
model: z.string().min(1),
}),
)
.mutation(async ({ input }) => {
try {
const provider = selectAIProvider({
apiUrl: input.apiUrl,
apiKey: input.apiKey,
});
const model = provider(input.model);
const result = await generateText({
model,
prompt: "Reply with 'ok'",
});
if (!result.text) {
throw new Error("No response received from the model");
}
return { success: true, message: "Connection successful" };
} catch (error) {
throw new TRPCError({
code: "BAD_REQUEST",
message:
error instanceof Error
? error.message
: `Connection failed: ${error}`,
});
}
}),
suggest: protectedProcedure
.input(
z.object({
aiId: z.string(),
input: z.string(),View on GitHub (pinned to 546686ea35)
Solutions
- Verify notifications schema (required columns, destination-type enum includes 'telegram')
- Apply pending migrations
- Test the raw INSERT to identify the violated constraint
Defensive patterns
Strategy: validation
Validate before calling
if (!input.name?.trim()) throw new Error('Notification name is required'); Try / catch
try { await createTelegramNotification(input); } catch (e) { if (e?.message?.includes('Inserting notification')) { /* verify notifications schema */ } throw e; } Prevention
- Keep notifications enum/constraints in sync with new providers
When it happens
Trigger: The notifications insert violating NOT NULL/enum constraints (missing name or destination type not accepting 'telegram'), or aborted transaction from the prior statement.
Common situations: Schema drift on notifications; new required column added without default.
Related errors
AI-assisted analysis of Dokploy/dokploy@546686ea35 (2026-08-27).
Data as JSON: /api/errors/0d517377c7f0c1ef.
Report an issue: GitHub.