TSS Update on June 5, 2022
The previously announced update of the SIGN DE API on Sunday, June 5, 2022 is postponed. Therefore, the scheduled maintenance is no longer necessary and is canceled. You can find more information in our related blog post Postponed Update
Here you find more information on our scheduled maintenance on June 5, 2022. We will update our system to make it even better.
SIGN DE - TSS Update Announcement
Scheduled Maintenance Sunday, June 5, 2022, 08:00-16:00 CET SIGN DE API will undergo scheduled maintenance on Sunday, 5.6.2022, between 08:00 and 16:00 (CET).
The maintenance will involve a rolling update of LIVE TSS instances from version 1.0.5-1.2.0 to version 1.0.6-1.3.0 (where the former is the SMAERS version and the latter is the CSPL version).
During the maintenance window, the following restrictions apply:
- Data Exports are disabled.
- TSS state transitions to
DISABLEDare not possible. - API calls may take longer than usual or run into timeouts.
- Service interruptions may occur.
Note for June 6, 2022
As a consequence of the TSS update, on June 6, 2022 between 05:00 and 08:00 (CET) the first request to a TSS may take up to 15 seconds.
FAQ of TSS Update
Below you can find answers to some questions you may have on the TSS update on June 5, 2022.
What does the update entail?
The update concerns the deployment of the new certified versions for the SMAERS (from version 1.0.5 to 1.0.6) and CSPL (from version 1.2.0 to 1.3.0), together representing an update of the entire TSS to version 1.0.6-1.3.0.
The TSS update will also represent the deployment of version 2.1.0 of SIGN DE API.
You can find the certification documents for the new versions at Certification | fiskaly.developer.
What are the effects of the update?
The new versions of SMAERS and CSPL include bugfixes and stability improvements. Customers' operations should not be affected, as there are no changes to the API. The only visible differences are in the exports triggered after the update: the exports will include the update logs, and the TSS version in the info.csv will be incremented to 1.0.6-1.3.0. Old exports, i.e. exports triggered before the update, will not be affected by it.
Only TSS instances that are in the states UNINITIALIZED or INITIALIZED will be updated. All existing and new TSS instances in the state CREATED will be in the new version once they are transitioned into the UNINITIALIZED state. An update of DEFECTIVE and DISABLED instances is not possible due to technical reasons.
Customers may experience some temporarily increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.
What do I need to do?
Customers do not need to do anything on their side. As mentioned above, there are no effects on customer operations apart from some restrictions and the inevitable interruptions during the update process.
We recommend to follow our guide on how to deal with service interruptions and timeouts at Error and Timeout-Handling | fiskaly.developer.
After the update is completed, you can verify the update by checking your info.csv files in the data exports of INITIALIZED TSS instances for the correct TSS version.
Can I continue to use SIGN DE API during the update timeframe?
In principle, yes. During the maintenance window, individual calls may fail, time out or take longer than usual.
Data Exports and the TSS state transition to state DISABLED will also be temporarily disabled during the maintenance window. HTTP endpoints regarding these operations will respond with HTTP status code 503.
Otherwise SIGN DE API will remain available and functional throughout the maintenance window.
When will the update take place?
The update will take place as a rolling update over longer periods of time during the announced maintenance window. It does not mean that it will start at exactly 8:00 or last until exactly 16:00, but during that period different parts of SIGN DE API will be updated at various times.
What does it mean that the data exports are disabled?
During the maintenance window the export endpoints will return HTTP status 503.
How long will the data exports be disabled?
The data exports may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding data exports during the maintenance window entirely.
How long will the TSS disabling functionality be disabled?
The TSS disabling functionality may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding setting TSS instances to state DISABLED during the maintenance window entirely.
What does it mean that service interruptions can occur?
In addition to the disabled functionality, during the rolling update process, individual TSS instances may be temporarily unreachable or busy as their components are being updated.
Some TSS instances may temporarily display increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.
Happy updating, the fiskaly SIGN DE Team