Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 7397 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Command Bundles / Installations

Berlin

One more question...how long are transfered task bundles or other commands like installations "valid"? I have found out that most of my commands/installations are "completly failed" when the device is not turned on within 6 hours. Most of my devices are "offline" for at least 12 hours per day...so this does not work for me. Only way to avoid failed installations was to transfer task bundles at a specific time and date (every 6 hours). Is there any other way to avoid failed installations or to extend the time until an installation gets "completly failed"?

Greetings from Germany!

:54491


This thread was automatically locked due to age.
  • 0

    Can anybody help me? We still have the same problem...

    :54958
  • 0

    Hi Berlin,

    configuring the validity of tasks is not possible at the moment via the SMC console.

    By default, every task should be retried 5 times with a delay of 48 hours.

    Therefore, it is a bit strange, that your task immediately switch to the "Completely failed"  status.

    This only occurs if the SMC Server immediately recognizes that it does not make sense to sent out the task (e.g. because of APNS is invalid or a placeholder could not be replaced).

    If you want the issue to be analyzed, I would suggest to create a support ticket and provide a set of SMC log fiiles which cotain the time where this issue occured.


    Best regards

    Stefan

    :54986
Unfiltered HTML