How To Fix TT349 - The start action was canceled in number & of & runs

TT349 - Overview

• Message type: E = Error

• Message class: TT - Extended Computer Aided Test Tool (eCATT) messages

• Message number: 349

• Message text: The start action was canceled in number & of & runs

What causes this issue?

When the log was formatted, a running transaction in a CATT procedure
has probably terminated.

System Response

It is fundamentally impossible to tell from the CATT log, when a
transaction is terminated, because that terminates the complete CATT
session. The log can then not be completed and closed. It is always
possible that the transaction is still active.
The only indication is the elapsed time. The log assumes that a
transaction has terminated if it started more than 20 minutes
previously.
If less than 20 minutes have elapsed, the message TT 148: 'The
procedure has been active
for & minutes' is entered in the log.

How to fix this error?

As the function refresh is no longer available after more than 20
minutes of transaction time, the log can be refreshed via F3 'Back' and
re-selection. It is possible that the CATT procedure may have
progressed in the meantime, if it contains long-running transactions.
As this becomes ever less likely as time passes, you should look for
the cause of termination in the system log.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TT349 - The start action was canceled in number & of & runs ?

  The SAP error message TT349, which states "The start action was canceled in number & of & runs," typically occurs in the context of SAP's background processing or job scheduling. This error indicates that a scheduled job or action was not able to start as expected, and it provides information about the number of runs affected.
  Causes:
  
  Job Cancellation: The job may have been manually canceled by a user or an administrator.
  Resource Issues: There may be insufficient resources (e.g., memory, CPU) available to start the job.
  
  Configuration Issues: Incorrect configuration settings for the job or the system may prevent it from starting.
  Dependencies: The job may depend on other jobs or processes that have not completed successfully.
  Authorization Issues: The user or process attempting to start the job may lack the necessary authorizations.
  System Errors: There may be underlying system errors or issues that are preventing the job from starting.
  
  Solutions:
  
  Check Job Status: Use transaction codes like