I think it is more unfair to the end user of recent releases by not passing on
the benefit by providing an optimization or fix for an issue just because it
was uncovered/hit late! And especially when the fix does not create any harm
and only helps in succeeding the campaign. May be in the case
Just as a note - previously, I had a discussion with Ingvar and he had agreed
to convert this into a defect.
I can provide a patch for this for OM api calls except for the CCB APIs (based
on the description above).
Should we also give this treatment for OI APIs?
---
** [tickets:#1448] smf:
- **Comment**:
I think this ticket has to be treated as a defect because
- this behaviour (IMM returning NO_RESOURCES) and the expectation from the
immuser to treat it as try_again seems to be existing atleast as old as the
4.5.x branch.
- handling this error code as a try_again seems to be
There are at least three points to make in response to the claim that this has
to be a defect.
1) We have not seen this problem earlier. So obviously testing is different
this time, i.e. this
is new way of testing that was not performed when testing the earlier
releases.
2) Saying
I should also clarify that there is a distinction between (a) getting
ER_NO_RESOURCES as the direct
result from an IMM API call (in the above case a search or accessorGet used by
SMF); and (b) determining that a CCB was aborted due to resource error and not
validation error (new API
---
** [tickets:#1448] smf: Make campaigns less fragile by retrying on
ERR_NO_RESOURCES**
**Status:** unassigned
**Milestone:** future
**Created:** Fri Aug 14, 2015 07:09 AM UTC by Anders Bjornerstedt
**Last Updated:** Fri Aug 14, 2015 07:09 AM UTC
**Owner:** nobody
The SMF service is a
