Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/android/AddMinutesToDateTime.java`:
- Around line 87-113: The try block around DateTimeFormatter.ofPattern(...) and
the parsing in AddMinutesToDateTime (the code that uses
inputFormatter/outputFormatter, LocalTime.parse/LocalDateTime.parse, plusMinutes
and format) must also handle IllegalArgumentException thrown for invalid pattern
strings; update the error handling by adding a catch for
IllegalArgumentException (or use a multi-catch: catch (DateTimeParseException |
IllegalArgumentException e)) and in that catch log a clear warning (logger.warn)
with the message, call setErrorMessage(...) with the same actionable text, and
return null—mirroring the existing DateTimeParseException handling so invalid
format patterns are caught and reported.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/android/SubtractMinutesToDateTime.java`:
- Around line 17-18: The user-facing annotation text for
SubtractMinutesToDateTime incorrectly uses "to" instead of "from"; update the
`@Action` annotation on class SubtractMinutesToDateTime by changing the actionText
and description strings to use "from" (e.g., "Subtract minute minutes from the
input-datetime..." and "...Subtracts specified minutes from a given input
datetime...") and scan the class for any other user-facing strings or Javadoc in
SubtractMinutesToDateTime that repeat "to" so they are also changed to "from"
for consistency.
- Around line 90-106: The branch that checks inputFormatString.contains("HH") is
unreliable; replace it by parsing with the DateTimeFormatter.parseBest approach:
use inputFormatter.parseBest(dateTimeString, LocalDateTime::from,
LocalTime::from) to get a TemporalAccessor, test whether the parsed result is a
LocalTime or LocalDateTime, then subtract minutesToSubtract and format with
DateTimeFormatter.ofPattern(outputFormatString) as before; update the logic
inside the SubtractMinutesToDateTime class where inputFormatter,
outputFormatString, minutesToSubtract and logger are used so you call parseBest
on inputFormatter, cast to LocalDateTime or LocalTime accordingly, do
minusMinutes, log the appropriate message, and return the formatted string.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/ios/AddMinutesToDateTime.java`:
- Around line 90-103: The routing logic using inputFormatString is too
permissive: before calling LocalTime.parse(dateTimeString, inputFormatter) (and
creating newTime), ensure the format contains no date tokens (e.g., "y", "yyyy",
"M", "MM", "d", "dd") so only pure time formats hit the LocalTime branch;
otherwise route to LocalDateTime.parse(dateTimeString, inputFormatter) (the
existing LocalDateTime/newDateTime branch). Update the condition around
inputFormatString (used with LocalTime.parse and LocalDateTime.parse) to check
for absence of date tokens or invert logic to detect date+time formats and
dispatch accordingly, keeping DateTimeFormatter outputFormatter and the
minutesToAdd logic intact.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/ios/SubtractMinutesToDateTime.java`:
- Around line 17-18: Update the user-facing grammar in the
SubtractMinutesToDateTime action annotation: change the phrase "Subtract ...
minutes to the input-datetime" to "Subtract ... minutes from the input-datetime"
in both the actionText and the description attributes of the `@Action` on the
SubtractMinutesToDateTime class so the message reads correctly to users.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/mobileweb/AddMinutesToDateTime.java`:
- Around line 90-103: The branch selector currently uses
inputFormatString.contains("HH"|"mm"|"ss") and incorrectly chooses
LocalTime.parse for datetime patterns; update the condition so it only selects
the LocalTime path when the format contains time tokens AND does NOT contain any
date tokens (e.g., "y", "yyyy", "yy", "M", "MM", "d", "dd", "D", "u" etc.).
Specifically, change the check around inputFormatString (the if that controls
LocalTime.parse and LocalDateTime.parse) to confirm absence of date-specifier
substrings before calling LocalTime.parse, otherwise use LocalDateTime.parse and
the existing date-time handling.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/mobileweb/SubtractMinutesToDateTime.java`:
- Around line 90-106: The branch selection based on inputFormatString's
"HH/mm/ss" incorrectly treats full datetime patterns as time-only causing
LocalTime.parse to throw; update the logic in SubtractMinutesToDateTime (where
inputFormatString is checked and LocalTime.parse/LocalDateTime.parse are used)
to first detect date components (e.g., 'y', 'M', 'd', 'D', 'E') and only treat
the input as time-only when time tokens are present AND no date tokens exist, or
alternatively attempt LocalTime.parse in a try-catch and on
DateTimeParseException fall back to parsing with LocalDateTime.parse; ensure the
outputFormatter usage remains the same and log messages (logger.info) are
preserved for both branches.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/salesforce/AddMinutesToDateTime.java`:
- Around line 86-115: The addMinutesToDateTime method uses a brittle
format-string contains heuristic and should instead use
DateTimeFormatter.parseBest to detect whether input parses to a LocalDateTime or
LocalTime; replace the branch that checks inputFormatString.contains(...) with
parsing via DateTimeFormatter inputFormatter =
DateTimeFormatter.ofPattern(inputFormatString) and
inputFormatter.parseBest(dateTimeString, LocalDateTime::from, LocalTime::from)
to obtain either a LocalDateTime or LocalTime, then add minutes on the
appropriate type and format with outputFormatter; update error handling to
remain the same and consider extracting this parse-and-normalize behavior into a
shared utility used by addMinutesToDateTime and other add/subtract methods
(e.g., a method like parseToDateTimeOrTime).

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/salesforce/SubtractMinutesToDateTime.java`:
- Around line 90-106: The branch condition misclassifies full datetimes as
time-only; update the logic that checks inputFormatString so it looks for date
component tokens (e.g., "y", "yyyy", "M", "MM", "d", "dd" or specifically
"yyyy"/"MM"/"dd") and route to LocalDateTime.parse/LocalDateTime.minusMinutes
when any date tokens are present; only use
LocalTime.parse/LocalTime.minusMinutes when the format contains no date tokens.
Change the branches around LocalTime.parse and LocalDateTime.parse accordingly
(references: inputFormatString, LocalTime.parse, LocalDateTime.parse,
newTime.format, newDateTime.format).

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/windows/AddMinutesToDateTime.java`:
- Around line 90-103: The branch incorrectly treats any format containing time
tokens as time-only; update the condition that decides between LocalTime.parse
and LocalDateTime.parse so it only uses LocalTime when the inputFormatString
contains time tokens (e.g., "HH","mm","ss") AND does NOT contain date tokens
(e.g., "y","M","d" or full tokens like "yyyy","MM","dd"); locate the check using
inputFormatString and switch to a clearer predicate (e.g., check for absence of
date tokens or use a regex) and then call LocalTime.parse(dateTimeString,
inputFormatter) only for pure-time formats, otherwise use LocalDateTime.parse as
currently done for datetime strings and format with outputFormatter.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/windows/SubtractMinutesToDateTime.java`:
- Around line 90-106: The current guard using inputFormatString.contains("HH")
|| contains("mm") || contains("ss") is inverted and will try LocalTime.parse on
values that include dates; change the check to detect absence of date components
instead: if the inputFormatString does NOT contain any of 'y', 'M', or 'd'
(e.g., !inputFormatString.contains("y") && !inputFormatString.contains("M") &&
!inputFormatString.contains("d")) then treat as time-only and use
LocalTime.parse(...) / time.minusMinutes(...), otherwise parse as LocalDateTime
using LocalDateTime.parse(...) / dateTime.minusMinutes(...); keep using
inputFormatter, minutesToSubtract, outputFormatter and
new...format(outputFormatter) as before and update the conditional in the
SubtractMinutesToDateTime code accordingly.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/windowsadvanced/AddMinutesToDateTime.java`:
- Around line 90-103: The branch condition for time-only parsing is inverted:
currently it routes formats containing time tokens to LocalTime.parse (using
inputFormatter), which fails when the format also contains date tokens like 'y',
'M', or 'd'; change the condition to detect true time-only formats by confirming
the ABSENCE of date tokens (e.g. ensure !(inputFormatString.contains("y") ||
inputFormatString.contains("M") || inputFormatString.contains("d"))), then use
LocalTime.parse for that branch and LocalDateTime.parse for formats containing
date tokens; update the condition around inputFormatString (and keep using
inputFormatter, LocalTime.parse, LocalDateTime.parse, plusMinutes, and
outputFormatter) so date-bearing formats go to LocalDateTime.parse and pure-time
formats go to LocalTime.parse.

In
`@add_minutes_to_the_specific_date_time_and_store_the_output_in_specific_format/src/main/java/com/testsigma/addons/windowsadvanced/SubtractMinutesToDateTime.java`:
- Around line 17-18: The actionText in the `@Action` annotation of the
SubtractMinutesToDateTime class is worded incorrectly ("Subtract minute minutes
to the input-datetime..."); update the actionText string to read "Subtract
minute minutes from the input-datetime with input-datetime-format, convert to
output-datetime-format format, and store it in a runtime variable variable-name"
so the user-facing instruction uses "from" instead of "to" (leave the
description and other identifiers unchanged).
- Around line 90-103: The current heuristic in SubtractMinutesToDateTime uses
inputFormatString.contains("HH"|"mm"|"ss") and incorrectly sends mixed date-time
patterns (e.g., "yyyy-MM-dd HH:mm:ss") to LocalTime.parse; update the condition
to detect both date and time tokens: check for presence of any date-pattern
tokens (e.g., "y", "yyyy", "M", "MM", "d", "dd") AND any time-pattern tokens
("H","HH","m","mm","s","ss"); if both date AND time tokens are present, route to
LocalDateTime.parse(dateTimeString, inputFormatter) and use
newDateTime.minusMinutes(minutesToSubtract), otherwise if only time tokens use
LocalTime.parse(...) and newTime.minusMinutes(...), and if only date tokens
handle accordingly (or throw a clear error). Ensure you update the branches
around inputFormatter, LocalTime.parse, LocalDateTime.parse, newTime/newDateTime
and the returned formatted result.