Use “Railway deployment log brief” in Recued. It provides a read-only Railway deployment investigation brief.

How it works 14 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (14 steps)

■ target_deployment_id trim

Trim whitespace from setting deployment id

■ normalized_log_filter trim

Trim whitespace from setting log filter

◆ deployment recued-core.railway.deployment.read

Read deployment on railway

◆ runtime_logs_raw recued-core.railway.deployment.log.search

Search deployment log on railway

◆ build_logs_raw recued-core.railway.build.log.search

Search build log on railway

■ defaults defaults

Apply defaults

■ runtime_log_count count

Count items in runtime logs

■ build_log_count count

Count items in build logs

✦ summarize core.ai.summarize

AI generates a concise summary

■ runtime_rows slice

Take a subset of

■ build_rows slice

Take a subset of

■ runtime_table to_table

Format results as a data table

■ build_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

▼

Output

summary card

table runtime_table

table build_table

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the Railway deployment status and logs. Identify likely failure signals, rollout state, rollback/redeploy availability, and concrete next checks. Quote only short log fragments and do not invent facts outside the Railway data.

log limit setting = 100

row limit setting = 25

log filter setting =

max length setting = 1000

deployment id setting =