Hi all, I'm using a stored process (SP) in a SAS CI360 decision flow that updates data on Teradata successfully — the SQL logic executes correctly, no errors appear in the SAS log, and I can confirm the database is updated. However, the CI360 flow node returns an "Error" status, even though everything ran as expected. 🔍 Context: The SP receives a segmentName prompt from CI360. It connects to Teradata and runs an UPDATE (e.g., sets EMAIL_STATUS = 1). %maspinit, %MAcount, and %MAstatus macros are used. In some SPs, a work. dataset is created (work.Updated_Customers), others don't return any dataset. The SP does not produce ODS output or use file _webout, unless manually added. The SP is marked with the following properties: ✅ Stored Process Server Only ✅ Result Capabilities: Stream + Package are both checked. 💡 Interesting part: The exact same logic works fine in another SP that updates PUSH_STATUS instead of EMAIL_STATUS. The only differences are: Whether a segment is used in practice. Whether a dataset or output is explicitly returned. ❓ My Questions: What minimum output is required for a stored process to be considered "successful" by CI360? Does CI360 require: At least one SAS dataset in the work library? A valid %MAstatus() file to be written under _STPWORK? An ODS HTML or file _webout stream to be produced? Is it OK for a stored process to return nothing (no dataset, no stream), or will CI360 always interpret that as an error? 🎯 Goal: My stored process works fine in SAS and updates Teradata correctly, but CI360 seems to expect an output or a signal to consider the node successful. I’d like to understand what that expected behavior is so I can make all my SP nodes CI360-compliant. Thanks a lot in advance! (Viya environment + CI360 + Teradata)
... View more
