Snowpark feature generation failed error "stored procedure timeout after 60 minutes"

Not specified by the original author.

TL;DR

Split the feature generation by partition and raise the statement timeout for the session running the procedure, on a larger warehouse if the hour is compute bound, because a single unpartitioned procedure run hit the 60 minute ceiling before finishing all partitions. Start with the Snowpark stored procedure definition and the session parameters on the Snowflake worksheet or job, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Snowpark feature generation failed error "stored procedure timeout after 60 minutes"

Use this when

• You see this exact message or symptom: Snowpark feature generation failed error "stored procedure timeout after 60 minutes"
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Snowpark stored procedure definition and the session parameters on the Snowflake worksheet or job, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the procedure workload per partition, the statement timeout setting on the session, and the warehouse size and queueing during the run. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Split the feature generation by partition and raise the statement timeout for the session running the procedure, on a larger warehouse if the hour is compute bound, because a single unpartitioned procedure run hit the 60 minute ceiling before finishing all partitions. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the online and offline values for that entity agree
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Snowpark feature generation failed error "stored procedure timeout after 60 minutes"

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Snowpark Python stored procedures, Snowflake feature generation jobs, scheduled tasks.

Why it happens

Feature generation that grew with the table eventually crosses any fixed timeout. One monolithic call gives no partial progress, so every timeout loses the full hour instead of one partition.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_VjCmD4xh8VFVJ26g30cXGw

Resolved from the public thread: https://vectle.com/posts/pst_VjCmD4xh8VFVJ26g30cXGw

Thread query: Snowpark feature generation failed error "stored procedure timeout after 60 minutes"

TL;DR: Split the feature generation by partition and raise the statement timeout for the session running the procedure, on a larger warehouse if the hour is compute bound, because a single unpartitioned procedure run hit the 60 minute ceiling before finishing all partitions. Start with the Snowpark stored procedure definition and the session parameters on the Snowflake worksheet or job, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.